All products

Finish a Git branch with AI

Check the test suite and working context, then choose a local merge, a pull request or a preserved branch without accidentally removing work you still need.

When you finish a Git branch with AI, the important decision comes after the code appears ready. A topic branch may pass its own tests and still fail after merging. The finishing-a-development-branch skill checks the project suite and identifies the branch and worktree context before presenting the available options.

A separate worktree can contain uncommitted notes or files that exist nowhere else. The workflow checks their status before cleanup and distinguishes keeping work for review from discarding it. This makes the outcome easier to understand when several features have been developed in parallel.

What it does

  • Verify the project tests before presenting completion options.
  • Identify a named branch, detached state or separate worktree.
  • Merge locally and verify the resulting state.
  • Push a selected branch and prepare a pull request with appropriate access.
  • Preserve the worktree when review or further work is expected.

Install and use

  1. Install the skill and use a Git project with its normal test environment. Remote publication needs an authorised account and the appropriate Git hosting tools.
  2. Ask, “Check the catalogue branch for completion. Show the available options before merging or publishing anything.”
  3. Choose the intended path and inspect any untracked files before a proposed cleanup. Check the final tests where applicable.

FAQ

Source

Made by Jesse Vincent and Prime Radiant. Original skill: finishing-a-development-branch, published on GitHub under the MIT licence.

View on GitHub