Phase commit
Engineering workflows and standards for Codex and Claude Code: plan, implement, test, review, and deliver repository changes.
npx -y skills add yarlson/yarstack --skill phase-commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Create one local commit for a completed, validated, and reviewed unit of work. Use only when the user explicitly requests a commit without pushing or other delivery actions.
SKILL.md
1.4 KB, as published. Nobody here has run it
Phase Commit
Create one isolated local commit without changing history or external state.
Workflow
- Confirm required repository checks and applicable validation and review cover the exact intended content.
- Inspect status, staged and unstaged changes, and relevant untracked files; preserve all unrelated user work.
- Stop when scope is ambiguous or includes sensitive, unexpectedly generated, or otherwise unsafe paths.
- Stage only explicit paths with
git add -- <paths>; never use broad staging commands or globs. - Review the staged path list and diff against the requested unit.
- Draft the commit subject and body using repository conventions, then use
english-text-reviewand apply its material findings without changing technical meaning. - Commit without bypassing hooks or changing signing policy.
- Verify the created commit content and remaining worktree.
Do not amend, rewrite history, push, create branches or pull requests, manage CI, tag, release, or include unrelated changes.
On hook or commit failure, stop and report the blocker without claiming completion.
Finish only after verifying the created commit, then report its hash and concise summary.