finishing-branch

Guides completion of development branches through merge, pull request, or cleanup options.

Updated Oct 2, 2025
One-click install
npx skills add https://github.com/YuriiYInno/Innogram --skill finishing-branch-yuriiyinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-branch
Source: https://github.com/YuriiYInno/Innogram/tree/main/.codex/skills/finishing-branch
Command: npx skills add https://github.com/YuriiYInno/Innogram --skill finishing-branch-yuriiyinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementation work is done, developers often skip verification steps or fumble the final integration of a feature branch. This Skill enforces a structured finish: verify tests pass, then choose between merging locally, creating a pull request, keeping the branch, or discarding it safely. ## Core Features & Use Cases - Test Gate Before Integration: Runs test, lint, and build commands and stops the workflow if anything fails, preventing broken code from being merged. - Four Structured Completion Options: Presents merge-to-base, push-and-create-PR, keep-as-is, or discard choices, each with exact git commands and confirmation safeguards. - Worktree and Branch Cleanup: Removes worktrees and deletes branches after merging, or requires explicit typed confirmation before discarding work. - Use Case: After finishing a feature on a branch, invoke this Skill to verify the test suite, then push the branch and generate a GitHub pull request with a formatted summary and test plan via the gh CLI. ## Quick Start Use the finishing-branch skill to verify my tests pass and help me merge or create a pull request for this completed feature branch.

Frequently Asked Questions about finishing-branch

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

FAQPage Schema
How do I finish a feature branch after implementation is complete?▼

Verify tests, lint, and build pass first, then choose one of four options: merge locally into the base branch, push and create a pull request, keep the branch as-is, or discard it. Each option includes the exact git commands to execute.

How to create a GitHub pull request from the command line?▼

Push the branch with git push -u origin, then run gh pr create with a title and a body containing a summary of changes and a test plan checklist. The Skill generates this PR body template automatically.

What happens if tests fail before merging a branch?▼

The workflow stops immediately and does not present merge or PR options. You must fix the failing tests, lint errors, or build issues before the branch completion process can continue.

Can I delete a branch and its work without losing work accidentally?▼

The discard option requires explicit typed confirmation of 'discard' before permanently deleting the branch, its commits, and the worktree. Without that confirmation, no destructive action is taken.

Does this workflow clean up git worktrees after merging?▼

Yes, for the merge, pull request, and discard options it checks git worktree list and removes the associated worktree. The keep-as-is option deliberately preserves the worktree and branch.