Menu
Use when implementation is complete to verify and finalize work directly on main/master
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ê.
Use when you have a written implementation plan and need to execute it directly in the current session on main/master
Use when implementing small or low-complexity changes with minimal ceremony — modular, domain-centered behavior, clear separation from infrastructure, and practical SOLID guardrails without full hex/DDD layering
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use before writing an implementation plan — recommend lightweight vs heavyweight (hex-infra, DDD depth) from signals, confirm with the user, and record the decision for execution
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Use when you have a spec or requirements for a multi-step task, before touching code
Baseado na classificação ocupacional SOC
| name | finishing-a-development-branch |
| description | Use when implementation is complete to verify and finalize work directly on main/master |
Guide completion of development work in a no-branch flow.
Core principle: Verify tests → summarize changes → ask for commit decision.
Announce at start: "I'm using the finishing-a-development-branch skill to complete this work."
Before finalizing, verify tests pass:
# Run project's test suite
npm test / cargo test / pytest / go test ./...
If tests fail:
Tests failing (<N> failures). Must fix before completing:
[Show failures]
Cannot finalize this work until tests pass.
Stop. Don't proceed to Step 2.
If tests pass: Continue to Step 2.
# Must be main or master
git branch --show-current
If not on main or master, stop and ask the user how to proceed.
Present exactly these 2 options:
Implementation complete on <current-branch>. What would you like to do?
1. Commit changes now on <current-branch>
2. Keep changes uncommitted for now
Which option?
Don't add explanation - keep options concise.
git add <relevant-files>
git commit -m "<message>"
Report: "Keeping changes uncommitted on ."
| Option | Commit | Leave Uncommitted |
|---|---|---|
| 1. Commit now | ✓ | - |
| 2. Keep as-is | - | ✓ |
Skipping test verification
Open-ended questions
Never:
Always:
main or masterCalled by:
Pairs with: