A cleanup routine for local development after a GitHub pull request has been merged. It synchronizes the main branch, removes the finished branch and worktrees, updates the related issue, and records lessons.

Use it after a merge to update local main, delete merged branches, remove temporary worktrees, close the linked issue, and capture review learnings.

It prevents leftover branches, worktrees, and outdated issue labels from cluttering the project. It also keeps local files and project tracking aligned with the merged code.

after-merge — Command for Claude Code by xsovad06: A cleanup routine for local development after a GitHub…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/xsovad06/sova/after-merge

Clone the repo

git clone --depth 1 https://github.com/xsovad06/sova

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/xsovad06/sova/after-merge.svg)](https://agentmods.dev/commands/xsovad06/sova/after-merge)

Your own site

<a href="https://agentmods.dev/commands/xsovad06/sova/after-merge"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/after-merge.svg" alt="Measured on agentmods" height="20"></a>

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 536 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00027	$0.00536
Opus 5	$0.00014	$0.00268
Sonnet 5	$0.00005	$0.00107
Haiku 4.5	$0.00003	$0.00054

Measured 4d ago against content hash b1464e7140ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

after-merge scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/after-merge.md · 70 lines

What it actually says

After Merge Cleanup

Run this after a PR has been merged to clean up local state and capture learnings.

Instructions

Get the PR from $ARGUMENTS (PR number or branch name). If empty, check for recently merged PRs:
```
gh pr list --author @me --state merged --limit 5
```
Switch to main and pull:
```
git checkout main
git pull origin main
```
Delete the merged branch locally:
```
git branch -d <branch-name>
```
If the branch name isn't obvious: git branch --merged main

Clean up worktrees (if any exist for this ticket):

git worktree list

Remove worktrees for the merged ticket:

git worktree remove .claude/worktrees/<ID> --force 2>/dev/null || true

Close linked issue and clean up labels:

gh issue close <ISSUE_NUMBER> 2>/dev/null || true

Remove stale workflow labels that are no longer meaningful on a closed issue:

gh issue edit <ISSUE_NUMBER> --remove-label "agent:in-review" --remove-label "agent:in-progress" --remove-label "sova:revise" --remove-label "sova:block" 2>/dev/null || true

Capture learnings from the PR review (run /ingest-review workflow):
- Fetch PR review data
- Extract lessons: patterns to follow, mistakes to avoid, style preferences, test coverage gaps
- Update .claude/agent-memory/cookbook.md (under matching domain section)
Report what was cleaned up and what was learned.

Cross-References

Learning from the review: Calls /ingest-review internally
Extract broader knowledge: Run /extract-knowledge if significant patterns emerged
Ready for next task? Run /find-task or /standup

Rules

NEVER use emojis in any output

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

4d ago First seen · 70 lines · 27 tokens per session scan A b1464e7140ce

Subscribe to this mod's changes

after-merge is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 536 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Code review Git and workflow ai-agents automation autonomous-development cli developer-tools pr

after-merge

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

After Merge Cleanup

Instructions

Cross-References

Rules

What this file has done since we first saw it

Other commands, from other repositories

doctor

dashboard

greptile-review

update

pr-description-ja

pr-description-en