skills.rest
jrmatherly
jrmatherlyCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

shipit-kit:merged

Delete merged local git feature branches and update feature metadata.

1|Updated Apr 3, 2026
Search Tags:#automation#git#cli#branch-cleanup#post-merge#feature-yaml#shipit
One-click install
npx skills add https://github.com/jrmatherly/shipit --skill shipit-kit-merged
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shipit-kit:merged
Source: https://github.com/jrmatherly/shipit/tree/main/.claude/skills/shipit-kit-merged
Command: npx skills add https://github.com/jrmatherly/shipit --skill shipit-kit-merged

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the post-merge housekeeping that developers otherwise perform manually: switching back to the main branch, pulling the latest changes, updating feature metadata, and removing the local feature branch once a PR has been merged.

Core Features & Use Cases

  • Switch and sync: Switch to main and pull the latest commits to ensure local repository state matches the remote.
  • Feature metadata update: Mark a feature as complete in specs/NNN-feature-name/feature.yaml and commit the update before branch deletion.
  • Safe branch removal: Use a safe git branch -d deletion and surface a clear warning if the branch is not actually merged; suited for CI-driven workflows and multi-agent feature development.

Quick Start

Run the post-merge cleanup to mark the feature as complete in its specs, switch to main and pull the latest changes, and then safely delete the local merged branch.

Frequently Asked Questions about shipit-kit:merged

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

FAQPage Schema
How do I automatically clean up local git branches after a pull request is merged?▼

Automated post-merge branch cleanup switches your local repository to main, pulls the latest commits, updates feature metadata, and safely deletes the merged feature branch using git branch -d.

What is the safest way to delete a local feature branch after merging to main?▼

Safe post-merge branch deletion uses git branch -d, which verifies the branch is fully merged before removing it, and surfaces a clear warning if the branch contains unmerged commits.

How do I update feature.yaml lifecycle metadata when a feature branch is merged?▼

Updating feature.yaml lifecycle metadata involves marking the feature as complete in specs/NNN-feature-name/feature.yaml, committing that update, and pushing the changes to main before local branch deletion.

Can I automate git branch cleanup for CI-driven workflows and multi-agent development?▼

Yes, this post-merge cleanup process is suited for CI-driven workflows and multi-agent feature development, synchronizing local state with the remote and ensuring safe deletion of merged branches.

What happens if I try to delete a local git branch that is not fully merged?▼

If the branch is not actually merged, the safe git branch -d deletion will fail and the process will surface a clear warning, preventing accidental loss of unmerged commits.

Related Skills

Explore More Software Engineering Skills→
jrmatherlyjrmatherly
1

shipit-kit:plan

Generate TDD implementation plans and tasks.yaml from feature specs and research.yaml.

Community
Advanced
bswrundquistbswrundquist

push

Push local commits to a remote Git repository with safety checks.

Community
Intermediate
blakecyzeblakecyze
2

kanso-pr

Generate pull request descriptions from commit history and repository templates.

Community
Intermediate
iani-kuliiani-kuli

create-branch

Create git branches with standardized names from user identity and diffs.

Community
Intermediate