Executes a gated branch-and-merge ritual for small single-issue fixes and chores.
npx skills add https://github.com/23min/aiwf --skill wf-patch-23min
Please help me install this Agent Skill. Skill: wf-patch Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded-rituals/plugins/wf-rituals/skills/wf-patch Command: npx skills add https://github.com/23min/aiwf --skill wf-patch-23min
git diff --cached) before and after dispatch, so subagent mutations cannot silently corrupt the commit. - Defect pinning and changelog discipline: Every defect fix lands with a regression test or gate rule, and every patch adds a CHANGELOG.md entry under ## [Unreleased], with named escapes stated at the commit gate. - Use Case: A user asks to fix a one-line bug tracked as gap G-0042. The Skill creates a patch/G-0042-fix-slug worktree branch, implements the fix with a regression test, runs the full local CI gate, obtains independent review, and walks through commit, merge, tracker closure (aiwf promote), cleanup, and push — each behind explicit approval. ## Quick Start Ask the assistant to run the wf-patch ritual to fix a specific small bug or typo on its own patch branch with review and approval gates.High-intent search queries and answers about installing and using this skill.
Use a patch workflow that cuts a dedicated branch from mainline in its own worktree, implements the fix with a regression test, runs the full local CI gate, and gets an independent reviewer to examine the staged diff. Commit, merge, and push each wait behind explicit human approval gates.
Use a patch when the change maps to one issue or a single-line summary, needs no spec or acceptance criteria, and lands in one merge to mainline. If unrelated changes get bundled, acceptance criteria emerge, or planning discussion starts, switch to a heavier milestone ritual.
Yes. A defect fix lands with the check that pins it, such as a failing-without-the-fix regression test or lint rule, and every patch adds a CHANGELOG.md entry under Unreleased. The only escapes are stated explicitly at the commit gate so the human can veto them.
Bundling hides outward or irreversible actions inside routine approvals. The commit gate covers the reviewed diff, the wrap gate covers an enumerated merge-close-cleanup sequence, and the push gate always stands alone because pushing is the only action that leaves the machine.
Any deviation from the approved wrap sequence, such as a merge conflict, check finding, or dirty state, aborts the sequence and re-gates from the point of deviation. A refused tracker closure means the merge did not land on mainline, so reconcile and merge first rather than forcing past the guard.
It does not write specs or acceptance criteria, run a full TDD cycle, or touch planning state and roadmaps. Changes needing test-first development escalate to a TDD cycle on the same branch, and patches stay off-roadmap by design except for closing the tracked item they fix.
go-musicfoxTriage tracker issues read-only to decide whether an autofix chain should proceed.
chrisbanesOperate a GitHub Project queue by claiming, planning, implementing, and merging issues.
KrishnatejavepaReview non-trivial code or design decisions with a fresh-context adversarial process.
Jimmy-JungGuide teams through a Red-Green-Refactor cycle for test-first development.