skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Testing & QA / Finishing A Development Branch Skill by @obra
The skill is the skills/finishing-a-development-branch folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
Guides what to do once implementation is complete and tests pass: verify tests, detect the environment, find the base branch and present integration options.
The original SKILL.md is organised into these sections:
Written and maintained by @obra. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
----|------|---------| | `GIT_DIR == GIT_COMMON` (normal repo) | Standard 3 options | No worktree to clean up | | `GIT_DIR != GIT_COMMON`, named branch | Standard 3 options | Provenance-based (see Step 6) | | `GIT_DIR != GIT_COMMON`, detached HEAD | Reduced 2 options (no merge) | Externally managed — leave in place | ## Step 3: Determine Base Branch The base branch is whatever this work forked from — usually named in the plan, the conversation, or the branch's upstream. If it is not already known, ask: "This branch split from <your best guess> - is that correct?" Confirm before merging: merging into the wrong base is expensive to undo. ## Step 4: Present Options **Normal repo and named-branch worktree — present exactly these 3 options:** ``` Implementation complete. What would you like to do? 1. Merge back to <base-branch> locally 2. Push and create a Pull Request 3. Keep the branch as-is (I'll handle it later) Which option? ``` …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.