shep-kit:merged

Switch to the main branch, pull updates, and delete the merged feature branch.

241|51|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/shep-ai/cli --skill shep-kit-merged
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shep-kit:merged
Source: https://github.com/shep-ai/cli/tree/main/.claude/skills/shep-kit%3Amerged
Command: npx skills add https://github.com/shep-ai/cli --skill shep-kit-merged

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a PR is merged, this Skill streamlines repository housekeeping by transitioning to the main branch, updating it, and removing the finished feature branch to keep the workspace clean.

Core Features & Use Cases

  • Switch to main and pull latest changes automatically.
  • Delete the local feature branch after a successful merge.
  • Works with common Git workflows and keeps local repos tidy.

Quick Start

Execute a post-merge cleanup on your current repository state by switching to main, pulling updates, and deleting the merged branch.

Frequently Asked Questions about shep-kit:merged

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

FAQPage Schema
How do I automate git post-merge cleanup to switch to main and delete a local branch?

You can automate git post-merge cleanup by switching to the main branch, pulling the latest updates, and deleting the finished local feature branch. This keeps your local repository tidy after a PR is merged.

What is the best way to keep my local git workspace clean after a pull request is merged?

The best way to keep a local git workspace clean after a PR merge is to transition to the main branch, update it with the latest changes, and remove the finished feature branch to prevent branch clutter.

Does post-merge branch cleanup work with standard git workflows?

Yes, post-merge branch cleanup works with common Git workflows that use standard branching semantics. It requires the git CLI to handle switching branches, pulling updates, and deleting local branches.

Do I need git CLI to automate switching to main and deleting a feature branch?

Yes, you need the git CLI to automate switching to main and deleting a feature branch. The process relies on standard git commands to pull updates and execute local branch deletion safely.

When should I delete a local feature branch in my repository?

You should delete a local feature branch when a pull request is successfully merged or when preparing to clean up your workspace. This housekeeping action ensures your repository remains organized and up to date.