finishing-a-development-branch

star 80

Use when implementation is complete and verified - delete finished local task docs, present integration options, and clean up safely

withzombies By withzombies schedule Updated 3/30/2026

name: finishing-a-development-branch description: Use when implementation is complete and verified - delete finished local task docs, present integration options, and clean up safely

This skill was ported from Claude Code. In Codex: - "Skill tool" means read the skill's `SKILL.md` from disk. - "TodoWrite" means create and maintain a checklist section in your response. - "Task()" means `spawn_agent` (dispatch in parallel when needed). - Claude-specific hooks and slash commands are not available; skip those steps. Finish work intentionally: verify the spec, decide how to integrate it, then delete the finished local task directory. MEDIUM FREEDOM - Verify first, then present integration choices and execute the chosen one without leaving stale local task docs behind. 1. Re-read `plan.md`, `context.md`, and `tasks.md` 2. Confirm acceptance checks and verification evidence 3. Present integration options: merge/PR, keep branch, discard branch 4. Delete the local task directory under `plans/active/` - Work is implemented and verified - The task directory is ready to close - The user needs a clean finish to the branch ## 1. Confirm the work is actually complete
  • tasks.md should have no active Now items
  • acceptance checks in plan.md should have evidence
  • verification should be fresh

2. Present the integration choice

Offer the user clear options:

  • merge or open PR
  • keep the branch for more work
  • discard the branch if the work should not land

3. Delete the local docs

Delete the completed local task directory from plans/active/.

Install via CLI
npx skills add https://github.com/withzombies/hyperpowers --skill finishing-a-development-branch
Repository Details
star Stars 80
call_split Forks 15
navigation Branch main
article Path SKILL.md
More from Creator