finishing-a-development-branch

Guides users through test verification, merge, pull request, and branch disposition after development.

Updated May 7, 2026
One-click install
npx skills add https://github.com/TK-Evans01/tk-harness --skill finishing-a-development-branch-tk-evans01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: finishing-a-development-branch
Source: https://github.com/TK-Evans01/tk-harness/tree/main/plugins/tk-rpie/skills/finishing-a-development-branch
Command: npx skills add https://github.com/TK-Evans01/tk-harness --skill finishing-a-development-branch-tk-evans01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, tk-rpie:librarian, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers complete their development work by guiding them through structured options for merging, creating a pull request, keeping the branch as-is, or discarding the work.

Core Features & Use Cases

  • Test Verification: Before presenting options, verifies that all tests have passed.
  • Branch Merging: Offers options for merging the feature branch back to the base branch.
  • Pull Request Creation: Assists in pushing the branch and creating a pull request.
  • Branch Preservation: Allows keeping the branch as-is for future use.
  • Branch Discard: Offers an option to discard the branch permanently.
  • Project Context Update: Updates the project context by invoking tk-rpie:librarian.
  • Worktree Cleanup: Cleans up the worktree for the feature branch after the chosen action is taken.
  • Test Plan Reminder: Reminds users to review the human test plan if one exists.
  • Quick Reference: Provides a quick reference table outlining the actions taken for each option.

Quick Start

Use the finishing-a-development-branch skill to complete this work.

Frequently Asked Questions about finishing-a-development-branch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I merge a development branch back to the base branch after tests pass?

To merge a development branch, the workflow first verifies all tests pass, then offers structured options to integrate your feature branch back into the base branch. It also cleans up the feature worktree after the merge is complete.

Can I create a pull request directly from a feature branch using this workflow?

Yes, you can create a pull request. The workflow assists in pushing your feature branch to the remote repository and initiating the pull request creation process as one of its core branch completion options.

Do I need git installed to automate branch management and worktree cleanup?

Yes, you need git installed. The workflow requires git for executing branch operations such as merging, discarding, and cleaning up the worktree for the feature branch after your chosen action is taken.

What is the best way to discard a development branch permanently?

The best way to discard a development branch is using the workflow's dedicated discard option, which permanently removes the branch and cleans up the associated worktree after verifying test status.

Does branch management require updating project context after merging?

Yes, branch management requires updating project context after merging. The workflow invokes tk-rpie:librarian to update project context and reminds you to review the human test plan if one exists.