Git

Route first: each action's actual rules live in a references/ file. Open the matching one before planning or acting; rules like commit grouping and branch naming shape the plan, so reading them late means redoing it. Several actions, several references.

Router

Branches (create, name, stack) -> references/branches.md Switching branches, naming rules, ticket references, switching with a dirty tree, stacked PRs (conventions here, mechanics via the gh-stack skill), the gh-stack/manual path probe, cascade conflicts and verification, manual restacking fallback (after merge, chain of 3+, mid-stack push), force-pushing.

Committing -> references/commits.md Pre-staging walk, file confirmation, message style, hook-failure handling, scoping, editor-free squash, empty commits.

Pull Requests (open, update) -> references/pull-requests.md Pre-flight survey, title format (including the stacked [n/N] marker), gh pr create flags, post-create lines, finishing PRs after gh stack submit, updating a body without clobbering it.

PR body (write or rewrite a description) -> references/pr-body.md Voice for the product and engineer blocks, each block's rule in body order, where a visual sits and when to take a screenshot, receipts and the structure hook, the skeleton, linking, AI footers.