skills.rest
agorokh
agorokhCOMMUNITY
Explore all skills by this author →
GitHub

post-merge

Sync local main, classify merged PRs, and update vault handoff documents.

Updated Jul 5, 2026
Search Tags:#workflow automation#gitHub#branch cleanup#pr merge#repo synchronization#vault handoff#diff classification
One-click install
npx skills add https://github.com/agorokh/applied-ai-research --skill post-merge-agorokh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: post-merge
Source: https://github.com/agorokh/applied-ai-research/tree/main/.cursor/skills/post-merge
Command: npx skills add https://github.com/agorokh/applied-ai-research --skill post-merge-agorokh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents post-merge delivery gaps by syncing the local main branch, classifying the merged PR’s impact, and updating the repository vault handoff so humans can quickly resume where work stands.

Core Features & Use Cases

  • Deterministic repo sync: Safely stashes WIP, merges PR (if still open), fast-forwards local main, and cleans only the merged PR head branch.
  • Automated PR classification: Runs a deterministic classification step for the merged PR and surfaces any linked-issue state.
  • Vault handoff updates: Performs an LLM judgment stage and then commits only scoped edits under docs/01_Vault, creating a vault-only PR for auto-merge.

Quick Start

Run post-merge for your PR number P so the repo syncs to main, the PR is classified, and the vault handoff is updated via a vault-only PR.

Frequently Asked Questions about post-merge

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

FAQPage Schema
How do I automate GitHub branch cleanup and local main synchronization after a PR merge?▼

Automating GitHub branch cleanup and local main synchronization after a PR merge requires safely stashing work-in-progress, fast-forwarding local main, and deleting the merged PR head branch. This process ensures your repository reflects the latest origin state without losing uncommitted changes.

What is the best way to update project documentation automatically when a pull request is merged?▼

Updating project documentation automatically when a pull request is merged involves classifying the PR impact and committing scoped edits to a vault handoff directory. This creates a separate vault-only pull request to track delivery notes and resume guidance.

How does PR diff classification help with post-merge repository stewardship?▼

PR diff classification improves post-merge repository stewardship by applying deterministic rules to evaluate the merged changes and surface linked-issue states. This classification step ensures human-readable delivery updates accurately reflect what actually shipped.

Can I use workflow automation to enforce safety constraints like no direct pushes to main?▼

Workflow automation can enforce safety constraints like no direct pushes to main by structuring post-merge actions into sync, classify, and vault phases. It ensures repository updates happen through scoped vault-only diffs and automated pull requests rather than direct commits.

Why does local main lag behind origin after completing a GitHub PR merge?▼

Local main lags behind origin after completing a GitHub PR merge because the remote merge updates the origin branch immediately, while your local repository requires an explicit fast-forward or pull operation to synchronize the new commit history.

Do I need a specific docs vault directory structure for automated PR handoff updates?▼

Automated PR handoff updates require a scoped docs directory structure, specifically a docs/01_Vault workflow path. The automation restricts all documentation edits to this vault location to ensure strict vault-only diffs in the generated pull request.

Related Skills

Explore More Software Engineering Skills→
CareCard-caCareCard-ca

github-pr-merge-cleanup

Merge GitHub pull requests and clean up branches after validation.

Official
Advanced
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
pradeepmoulipradeepmouli
2

speckit-issuesync.after-specify

Sync linked issue statuses after the after_specify hook in speckit workflows.

Community
Intermediate
OpenSourcePharmaFoundationOpenSourcePharmaFoundation
4

branch-cleanup

Identify stale or merged Git branches and delete them after user approval.

Community
Intermediate