skills.rest
Jerrylalala
JerrylalalaCOMMUNITY
Explore all skills by this author →
GitHub

finishing-a-feature

Verifies tests and integrates completed feature branches via merge, pull request, or push.

6|2|Updated Jan 30, 2026
Search Tags:#git#pull request#worktree#merge#feature branch#test verification#github cli
One-click install
npx skills add https://github.com/Jerrylalala/compound-engineering --skill finishing-a-feature-jerrylalala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finishing-a-feature
Source: https://github.com/Jerrylalala/compound-engineering/tree/main/plugins/compound-engineering/skills/finishing-a-feature
Command: npx skills add https://github.com/Jerrylalala/compound-engineering --skill finishing-a-feature-jerrylalala

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a feature branch is done, developers often skip test verification or fumble the final integration steps, leading to broken main branches and inconsistent Git history. This Skill enforces a standardized completion flow that validates tests first, then guides the merge, PR, or push decision. ## Core Features & Use Cases - Mandatory Test Gate: Runs the full test suite and blocks the workflow entirely if any test fails, with no skip option. - Four Integration Options: Presents direct merge, PR with branch retention, PR with local branch deletion, or push-only, matched to scenarios from hotfixes to team code review. - Worktree Cleanup: Detects worktree-based work and offers to remove the worktree after integration. - Use Case: After finishing a feature on a branch, invoke this Skill to confirm all tests pass, then create a GitHub PR against main with gh pr create and clean up the local branch in one guided flow. ## Quick Start Use the finishing-a-feature skill to verify my tests pass and help me integrate this feature branch into main.

Frequently Asked Questions about finishing-a-feature

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

FAQPage Schema
How do I finish a Git feature branch and merge it into main?▼

First verify all tests pass, then checkout the base branch, pull the latest changes, and merge with git merge --no-ff to preserve branch history. Push the base branch and delete the local feature branch with git branch -d.

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

Push your feature branch with git push origin, then run gh pr create with the --base and --head flags plus a title and body. The GitHub CLI opens the PR against your chosen base branch.

What happens if tests fail before merging a feature branch?▼

The workflow terminates immediately with no option to skip or continue. You must fix all failing tests and re-enter the completion flow, since merging broken code into the base branch is blocked by design.

Should I merge directly or create a pull request for my feature?▼

Direct merge suits small changes, hotfixes, and solo projects, while pull requests fit team collaboration requiring code review. The Skill presents four options including PR with branch retention or deletion and push-only for later handling.

How do I clean up a Git worktree after finishing a feature?▼

Navigate back to the original directory and run git worktree remove with the worktree path. The Skill prompts for this cleanup step automatically when it detects the work was done inside a worktree.

Related Skills

Explore More Software Engineering Skills→
moberghrmoberghr
6

using-git-worktrees

Create and manage git worktrees with branch naming and baseline tests.

Official
Intermediate
cmbayscmbays

learnings-synthesis

Synthesize cross-cutting patterns from a vertical's build cycle into learnings documents.

Community
Advanced
limaonlimaon

requesting-code-review

Evaluate code changes for quality and compliance before merging.

Community
Basic
HomericIntelligenceHomericIntelligence
18

verify-pr-ready

Validate GitHub Pull Requests for CI status, approvals, and merge conflicts.

Official
Intermediate