Stats
Actions
Tags
From psd-coding-system
Clean up merged branches, close issues, and extract compound learning insights
How this skill is triggered — by the user, by Claude, or both
Slash command
/psd-coding-system:clean-branchclaude-opus-4-6This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You've just merged a PR to dev. Now complete the post-merge cleanup workflow.
You've just merged a PR to dev. Now complete the post-merge cleanup workflow.
First, determine what branch you're on and find the associated merged PR and issue:
# Get current branch name
git branch --show-current
# Find merged PR for this branch
gh pr list --state merged --head $(git branch --show-current) --limit 1
# Get full PR details to find issue number
gh pr view <PR_NUMBER> --json number,title,body
Perform standard cleanup operations:
# Switch to dev and pull latest
git checkout dev
git pull origin dev
# Delete local feature branch
git branch -d <BRANCH_NAME>
# Delete remote feature branch
git push origin --delete <BRANCH_NAME>
Close the GitHub issue with a summary of what was completed:
# View issue to understand what was done
gh issue view <ISSUE_NUMBER>
# Close issue with comment summarizing the work
gh issue close <ISSUE_NUMBER> --comment "Completed in PR #<PR_NUMBER>.
<Brief 1-2 sentence summary of what was implemented/fixed>
Changes merged to dev."
After you complete the cleanup, the telemetry system will:
meta/telemetry.json in the compound_learnings[] arrayThis analysis looks for:
npx claudepluginhub psd401/psd-claude-plugins --plugin psd-coding-systemEnd-of-workflow audit of GitHub issues, PRs, and branches. Verifies every touched resource is in the right state (closed when done, kept when ongoing, deleted when dead) via a Sonnet subagent, then executes safe actions and prints a report.
Merges open PRs in dependency order after CI/approval checks, closes linked issues from PRs or .claude-harness/features/active.json, deletes feature branches locally/remotely, prunes refs, and reports summary. Use for completing features, post-review merges, or release cycles.
Runs a 4-step PR close sequence: reviewer-summary comment, squash-merge with PR title as commit subject, delete remote branch, close linked tracker issues. Use when merging or closing a PR.