Menu
Implement one bounded change from conversation context or a named vault artifact through TDD, verification, code review, and commit.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use this skill to rebase gh-stack branches and resolve conflicts. Replaces raw git rebase for stack workflows. Triggers: restack, rebase, rebase on main, branches out of date, resolve conflicts.
Use this skill for GitHub Stacked PRs (gh-stack) stack status, branch creation, stack navigation, restructuring a stack, or general gh-stack operations. Replaces raw git checkout -b, git rebase, git push, and gh pr create for stack workflows.
Use this skill to push a gh-stack stack and create or update stacked pull requests. Replaces git push and gh pr create for stack workflows. Triggers: push, ship it, send this up, submit, update PRs, create PR, push stack, send PRs.
Use this skill to sync a gh-stack stack with its remote and trunk. Triggers: sync, update from main, update from trunk, pull trunk, refresh stack.
Use this skill for GitHub Stacked PRs (gh-stack) stack status, branch creation, stack navigation, restructuring a stack, or general gh-stack operations. Replaces raw git checkout -b, git rebase, git push, and gh pr create for stack workflows.
Use this skill to sync a gh-stack stack with its remote and trunk. Triggers: sync, update from main, update from trunk, pull trunk, refresh stack.
| name | implement |
| description | Implement one bounded change from conversation context or a named vault artifact through TDD, verification, code review, and commit. |
| disable-model-invocation | true |
Use conversation context as the source of scope and acceptance criteria. When the user supplies a vault artifact, load /vault, resolve it with vlt read, and treat it as implementation input without depending on its artifact type.
Inspect the relevant code and tests before editing. Ask for a missing decision only when it prevents a safe implementation.
Use /tdd at the agreed seams. Require observable acceptance criteria before changing behavior.
Run typechecking regularly, single test files regularly, and the full test suite once at the end.
Once the implementation and checks are green, use /code-review against the request and any supplied artifact.
Address confirmed findings, then use /commit to commit the work to the current branch. Report delivered behavior, verification, and remaining risk.
