skills.rest
gobikom
gobikomCOMMUNITY
Explore all skills by this author →
GitHub

prp-cleanup

Automate post-merge cleanup by verifying merge status, archiving artifacts, and deleting branches.

2|Updated Feb 3, 2026
Search Tags:#branch management#GitHub automation#artifact archiving#post-merge cleanup#PR cleanup
One-click install
npx skills add https://github.com/gobikom/prp-framework --skill prp-cleanup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prp-cleanup
Source: https://github.com/gobikom/prp-framework/tree/main/adapters/codex/prp-cleanup
Command: npx skills add https://github.com/gobikom/prp-framework --skill prp-cleanup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, github-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the post-merge cleanup process, ensuring that merged pull requests are properly archived and branches are deleted, preventing orphaned branches and stale artifacts.

Core Features & Use Cases

  • Post-Merge Verification: Checks the merge status of pull requests before cleanup.
  • Artifact Archiving: Saves related artifacts to prevent data loss.
  • Branch Deletion: Removes local and remote branches after verification.
  • Batch Cleanup: Supports batch deletion of all merged branches with a single command.
  • Dry Run: Provides a preview of cleanup actions without making any changes.

Quick Start

Run the prp-cleanup skill with the branch name to clean up a single branch, or use the --all flag for batch cleanup.

Frequently Asked Questions about prp-cleanup

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

FAQPage Schema
How do I automate post-merge cleanup for pull requests and delete branches?▼

Automating post-merge cleanup for pull requests involves verifying the merge status, archiving related artifacts, and deleting branches. The process supports batch operations and dry runs to safely remove orphaned branches.

What is the best way to delete multiple merged GitHub branches at once?▼

The best way to delete multiple merged GitHub branches is via batch cleanup operations. You can use a single command with an --all flag to perform batch deletion of all merged branches after verifying their status.

Do I need git and GitHub API access to automate PR cleanup?▼

Yes, you need both git and GitHub API access to perform PR cleanup. These dependencies are required to verify pull request merge statuses and execute local and remote branch operations effectively.

Can I preview branch deletion and artifact archiving before making changes?▼

Yes, you can preview branch deletion and artifact archiving before making changes by using a dry run. This feature provides a safe preview of all cleanup actions without actually deleting branches or modifying data.

Why does post-merge cleanup require artifact archiving before branch deletion?▼

Post-merge cleanup requires artifact archiving before branch deletion to prevent data loss. Saving related artifacts ensures historical data is properly recorded before the associated branches are permanently removed.

Related Skills

Explore More Software Engineering Skills→
icyzhicyzh
1

github-code-review

Analyzes git diffs and manages GitHub pull requests via API.

Community
Advanced
zhuangfanupupzhuangfanupup

package

Clean Python repository caches, build artifacts, and exposed secrets.

Community
Intermediate
alistairhendersoninfoalistairhendersoninfo

merge-pr

Merge GitHub pull requests after validating status, reviews, and CI results.

Community
Intermediate
Jesse-L-MJesse-L-M

ship

Automate the end-to-end ship workflow from branch detection to PR creation.

Community
Advanced