Git Workflow

Use for branch state, pull requests, CI/review feedback, or safe publication. Read repository instructions first. Never reset, clean, stash, discard unrelated work, force-push, merge, deploy, or mutate production as part of this skill.

Route

• branch/current state and publish: branch-and-sync.md;
• PR setup, target diff/body, CI and automated feedback loop: pull-request-lifecycle.md;
• human review body, general comment, or inline thread: human-review.md;
• non-blocking material-delivery learning: reflection.md.

Human feedback always takes human-review route, even for inventory or summary request. A comment is hypothesis, not authority.

End-to-end authorization

Before ordinary delivery, ask authorization for complete loop: branch/worktree selection where applicable, implementation, focused checks, local code-review pass, commit, push, PR create/update, then bounded CI/automated-feedback monitoring. Local-only work occurs only when explicitly requested.

This authorization never covers force push, merge/deploy, production mutation, posting/replying/resolving human feedback, or material scope expansion. Those need separate exact approval.