Skip to content

t1k:unity:mobile:floor-probing-pr

FieldValue
Modulemobile
Version3.65.6
Effortmedium
Tools—

Keywords: floor probing, floor-probing branch, floor-probing pr, open pr floor probing, ThirdPartiesConfig pr

/t1k:unity:mobile:floor-probing-pr
[--branch <name>]

Turns a t1k-unity-mobile-floor-probing-config diff into a PR that is opened AND merged into develop. Resolves every parameter (branch name, commit message, pathspec, base branch, PR title/body) and then hands the actual git mutations to t1k-git-manager — per rules/orchestration-rules.md (“ALL git operations … route through t1k-git-manager, never raw git in the main session”) this skill does not run git/gh itself in the main session.

  • In scope: planning + delegating the branch/commit/rebase/push/PR/merge sequence for the floor-probing config change, into develop.
  • Out of scope: editing the asset (t1k-unity-mobile-floor-probing-config), Jenkins (t1k-unity-mobile-floor-probing-jenkins), resolving unrelated dirty files (report, never sweep them into the commit), the release-branch resolve/push (owned by the router — see t1k-unity-mobile-floor-probing steps 4 and 6), watching CI before merge beyond what t1k-git-manager itself does.
  1. Precondition check (main session, read-only): git status --porcelain. Confirm the ONLY changed path is the resolved ThirdPartiesConfig.asset. If unrelated dirty files exist, STOP and report them — do not stash, add, or otherwise sweep them into this change (rules/parallel-teammate-git-index-race.md; also applies solo, in case this repo is a fleet worktree per this project’s own CLAUDE.md).
  2. Resolve the plan (main session, no mutation):
    • Branch name: feat/floor-probing unless the user names another, or it already exists locally (check git branch --list feat/floor-probing and ask before reusing/overwriting).
    • Base: origin/develop. Confirm it exists on the remote (git ls-remote --heads origin develop) before planning around it — this is an explicit user-stated base, not the pr-target-staging.md default, so use develop directly once confirmed to exist.
    • Commit: pathspec form only, git commit -m "<msg>" -- <resolved-asset-path> — message follows the target repo’s own conventional-commit vocabulary (check git log --oneline -20 for its scope/type conventions rather than assuming fix/chore).
    • PR: gh pr create --base develop --title ... --body ... naming what changed (enabled floor probing, grid URL, that the API key is deliberately plain-text-committed per the schema’s own design).
  3. Delegate the mutation to t1k-git-manager with the resolved plan above as the brief — new branch from origin/develop, pathspec-commit only the named asset path, rebase onto origin/develop, push, open the PR with the given title/body/base, then merge it (gh pr merge --merge once checks are green — this is the user’s own app repo, not a kit repo, so kit-pr-workflow-boundary.md’s hands-off stance on kit/foreign PRs does not gate merging your own just-opened PR here). State explicitly in the brief: do not touch any file besides the named asset path.
  4. Clean up: the feature branch should not survive the merge — many repos auto-delete the remote branch on merge (tolerate that as a no-op); if it doesn’t, delete both the local and remote copies (core t1k-git/references/branch-discipline.md — the delete-branch procedure moved there from the rule; the rule itself is now a short stub).
  5. Report the merged PR URL and the SHA it merged as, back to the caller (and to t1k-unity-mobile-floor-probing if chained — its step 4 needs that SHA to resolve the release branch).
  • Never let the commit sweep in unrelated dirty files — the pathspec form commits WORKING-TREE content at the named path only, but a broader git add/git commit -a upstream of this skill’s plan would defeat that; the brief to t1k-git-manager must name the exact path, never ./-A.
  • origin/develop must be confirmed to exist, not assumed — git ls-remote --heads origin develop before planning around it as a base.
  • This skill now merges the PR it opens (gh pr merge --merge, delegated to t1k-git-manager, never a raw gh call in the main session) — replacing the earlier “open only, never merge” scope. It does not babysit CI beyond what t1k-git-manager itself does, and it never touches a PR it did not open this run (see kit-pr-workflow-boundary.md for the kit-repo case, which does not apply here — this is the user’s own app repo).
  • If feat/floor-probing already exists locally or on the remote, ask before reusing it — a second floor-probing PR against a stale branch is a worse outcome than asking one question.

t1k-git-manager executes the branch/commit/rebase/push/PR/merge steps, per rules/orchestration-rules.md’s git-ops routing table. This skill’s own job — precondition check, plan resolution, brief construction, and reporting the PR URL — runs inline in the main session (judgment/planning, not a mechanical step this skill would delegate further).

  • t1k-unity-mobile-floor-probing — entry/router that chains this skill after the config edit
  • t1k-unity-mobile-floor-probing-config — produces the diff this skill commits
  • t1k-unity-mobile-floor-probing-jenkins — the define-symbol half, independent of whether a PR was opened
  • rules/branch-discipline.md, rules/parallel-teammate-git-index-race.md, rules/pr-target-staging.md