pre-merge-housekeeping

Bundles checkpoint, wiki, and memory documentation updates into one docs commit before PR merge.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/rpmcdougall/claude-skills --skill pre-merge-housekeeping-rpmcdougall
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pre-merge-housekeeping
Source: https://github.com/rpmcdougall/claude-skills/tree/main/skills/pre-merge-housekeeping
Command: npx skills add https://github.com/rpmcdougall/claude-skills --skill pre-merge-housekeeping-rpmcdougall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finishing a feature branch often leaves documentation scattered: checkpoint files, wiki pages, CLAUDE.md, and MEMORY.md all need updates, and doing them piecemeal produces messy multi-commit noise or forgotten stale docs. This Skill consolidates every pre-merge documentation task into a single clean docs commit on the feature branch before the PR is opened. ## Core Features & Use Cases - Checkpoint Generation: Creates a dated memory/checkpoint-YYYY-MM-DD-<topic>.md file capturing what shipped, pulled from conversation context only. - Wiki Synchronization: Greps docs/wiki/ for files mentioning the affected mechanic and proposes or applies concrete edits, such as new rows in a manual testing guide. - Staleness Checks: Re-reads CLAUDE.md and MEMORY.md to fix outdated phase status, feature lists, or claims, archiving superseded lines to memory/history.md when MEMORY.md exceeds 200 lines. - Use Case: You just finished a melee combat feature on a branch and are about to open a PR. Invoke this Skill to generate the checkpoint, update the wiki testing guide, refresh stale memory files, and land it all as one docs: commit. ## Quick Start Tell the assistant you are ready to merge and ask it to run pre-merge housekeeping on the current feature branch.

Frequently Asked Questions about pre-merge-housekeeping

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

FAQPage Schema
How do I bundle documentation updates before merging a PR?▼

Run this Skill on your feature branch before opening the PR. It generates a checkpoint file, scans the wiki for affected topics, checks CLAUDE.md and MEMORY.md for staleness, and commits everything as one docs commit.

What is a pre-merge housekeeping workflow in Git?▼

It is a documentation consolidation step that runs on the feature branch before merge. It batches checkpoint files, wiki edits, and memory file updates into a single commit rather than scattering them across multiple commits.

Can I run pre-merge housekeeping on the main branch?▼

No. The Skill explicitly stops if the current branch is main. Housekeeping must happen on the feature branch before the PR is opened, never after merge.

What happens if no wiki files are affected by my changes?▼

The Skill reports that nothing in docs/wiki/ is affected and skips that section entirely. It does not force unnecessary edits just to fill the commit.

When should I not use this documentation bundling approach?▼

Avoid it after a merge has already happened, since the workflow is designed strictly for pre-merge. Also skip it when the conversation lacks enough context to name the topic or summarize what shipped.