ce:compound-refresh

Refresh stale docs/solutions/ learnings and classify documents as Keep, Update, Consolidate, Replace, or Delete.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill ce-compound-refresh-xbpk3t
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:compound-refresh
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/ce-compound-refresh
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill ce-compound-refresh-xbpk3t

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill keeps docs/solutions/ accurate and trustworthy by detecting and repairing stale, drifting, or duplicated learnings and pattern documents after refactors, migrations, dependency upgrades, or when retrieved guidance appears outdated.

Core Features & Use Cases

  • Scope detection: Narrow by directory, frontmatter, filename, or content search; supports focused, batch, and broad workflows.
  • Interactive and Autofix modes: Interactive mode asks targeted questions for ambiguous cases; autofix mode applies safe edits, marks uncertain items stale, and never pauses for input.
  • Classification and actions: Classifies artifacts as Keep, Update, Consolidate, Replace, or Delete; updates references, merges subsumed docs, creates replacements when evidence is sufficient, and generates a clear Applied/Recommended report.
  • Document-set analysis: Detects overlap, identifies canonical docs, and recommends consolidation or deletion to reduce drift risk.
  • Reporting: Produces a final summary with successfully applied changes and recommended manual actions when permissions or confidence are limited.

Quick Start

Run a refresh across docs/solutions in autofix mode to automatically apply safe updates, mark ambiguous items stale, and generate a concise Applied and Recommended report.

Frequently Asked Questions about ce:compound-refresh

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

FAQPage Schema
How do I automatically repair stale documentation after a major code refactor?

Refreshing stale solution docs involves detecting broken references, classifying each document as Keep, Update, Consolidate, Replace, or Delete, and applying safe edits or marking them stale to keep pattern documentation accurate.

What is the best way to consolidate duplicated pattern documentation in a repository?

Consolidating duplicated pattern documentation requires analyzing the document set to detect overlap, identifying canonical docs, and recommending consolidation or deletion to reduce drift risk and maintain trustworthy learnings.

Can I run documentation maintenance non-interactively during dependency upgrades?

Yes, you can run documentation maintenance non-interactively by using autofix mode, which applies safe edits to outdated learnings, marks ambiguous items stale, and never pauses for input during dependency upgrades.

How do I detect and fix broken references in solution docs after a migration?

Detecting and fixing broken references after a migration involves running a scope detection process across the repository to find moved references, classify the affected documents, and update or replace them with sufficient evidence.

When should I use interactive review instead of autofix for repository documentation maintenance?

Use interactive review instead of autofix when handling ambiguous cases during repository documentation maintenance, as it asks targeted questions to classify artifacts accurately rather than marking uncertain items stale automatically.