fix(skills): grant the -C form and stop routing the root through a va…

[Liu233w]

…riable

Pinning git -C deadened every permission grant in this skill's own frontmatter. Bash rules match on command prefix, so git -C <root> status --short does not begin with git status, and the six Bash(git …:*) entries stopped matching the moment the pin landed — every state-gathering command now prompts. Adds Bash(git -C:*), plus the commands the body actually prescribes and the earlier list omitted: show, rebase, checkout, reset, rev-list for the squash and verification flows, cp for fixup scoping, and ./doit.sh for the per-commit checks.

python3 and sed stay unlisted on purpose. Both appear in the body, but pre-approving arbitrary code execution for the whole turn is a bad trade in a commit skill; the prompt is proportionate friction.

Resolving the root from the skill's base dir is right — a literal breaks under worktrees — but carrying it in ROOT= is not: shell state does not persist between tool calls, and three independent read commands are exactly what gets split into parallel calls. $ROOT is then empty and git -C "" falls back to the drifted cwd, reinstating the bug the pin exists to prevent while looking defended against it. The resolved path is now substituted into each command directly.

[mergify]

Queued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-28 17:06 UTC · Rule: default · triggered by rule automatic merge
• ❌ Checks failed · on draft merge queue: checking main (a9c99b2) and #256 together #257
• 🚫 Left the queue — 2026-07-28 17:10 UTC · at 32684579923736a33f7ba1de1a715d033708e818

This pull request spent 3 minutes 49 seconds in the queue, including 3 minutes 33 seconds running CI.

Waiting for

• check-success=validate

All conditions

• check-success=validate
• github-review-approved [🛡 GitHub repository ruleset rule Not allow pushing to main]
  • fix(skills): grant the -C form and stop routing the root through a va… #256

Reason

The merge conditions cannot be satisfied due to failing checks

• validate

Failing checks:

• ❌ validate (job log)

Hint

You may have to fix your CI before adding the pull request to the queue again.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

Requeued — the merge queue status continues in this comment ↓.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-29 00:47 UTC · Rule: default · triggered by @Liu233w with the merge queue checkbox
• ✅ Checks passed · on draft merge queue: checking main (a9c99b2) and #256 together #258
• ✅ Merged — 2026-07-29 00:50 UTC · at 32684579923736a33f7ba1de1a715d033708e818 · rebase

This pull request spent 3 minutes 29 seconds in the queue, including 3 minutes 9 seconds running CI.

Required conditions to merge

• check-success=validate
• github-review-approved [🛡 GitHub repository ruleset rule Not allow pushing to main]
  • fix(skills): grant the -C form and stop routing the root through a va… #256