ce:compound-refresh

Reviews and refreshes stale, drifted, or duplicate learning documents in docs/solutions/.

6|2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/Jerrylalala/compound-engineering --skill ce-compound-refresh-jerrylalala
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce:compound-refresh
Source: https://github.com/Jerrylalala/compound-engineering/tree/main/plugins/compound-engineering/skills/ce-compound-refresh
Command: npx skills add https://github.com/Jerrylalala/compound-engineering --skill ce-compound-refresh-jerrylalala

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Over time, a knowledge base of engineering learnings (docs/solutions/) drifts out of sync with the codebase: file paths move, recommended fixes become outdated, and duplicate documents silently contradict each other. This Skill audits those documents against the current code and keeps the knowledge base accurate. ## Core Features & Use Cases - Drift Detection and Classification: Cross-references each learning doc against the current codebase and classifies it as Keep, Update, Consolidate, Replace, or Delete based on evidence. - Interactive and Autofix Modes: Runs interactively with one-at-a-time questions for ambiguous cases, or fully unattended via mode:autofix which applies safe actions and marks uncertain docs as stale. - Document-Set Analysis: Detects overlapping, superseded, or contradictory docs and consolidates them into a single canonical source of truth. - Use Case: After months of refactoring, run the refresh to find learnings referencing deleted files, merge two docs covering the same auth problem, and generate a report of applied and recommended actions. ## Quick Start Ask the AI to refresh the experience library by reviewing docs/solutions/ for outdated or duplicate learnings, optionally passing a scope like a module name or mode:autofix.

Frequently Asked Questions about ce:compound-refresh

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

FAQPage Schema
How do I refresh stale documentation in docs/solutions/?▼

Invoke the compound-refresh skill with an optional scope argument such as a subdirectory name, module, tag, or keyword. It investigates each candidate doc against the current codebase, classifies it, and applies or recommends the appropriate maintenance action.

How do I run documentation refresh without answering questions?▼

Add mode:autofix to the arguments. Autofix mode skips all user questions, applies unambiguous actions like Keep, Update, Consolidate, and auto-Delete, marks ambiguous cases as stale, and produces a report of applied and recommended actions.

What happens to deleted learning documents?▼

Deleted docs are removed permanently from the working tree with no archive directory. Git history preserves every deleted file, so you can recover them later using git log with the diff-filter=D option on docs/solutions/.

When does the skill replace a learning instead of updating it?▼

Replace is chosen when the core recommended solution conflicts with current code, such as an architectural change or a different preferred pattern. Update is used only for cosmetic drift like moved paths, renamed classes, or broken links where the solution still holds.

Can the refresh detect duplicate or contradictory docs?▼

Yes. The document-set analysis phase compares docs sharing modules, tags, or problem domains across problem statement, solution shape, referenced files, and root cause. High overlap triggers consolidation into a canonical doc, and contradictions are flagged for immediate resolution.