Verified:GitHub

ce-compound-refresh

Review docs/solutions for drift against the current codebase and report changes.

Updated Mar 14, 2026

Search Tags:#automation #codebase #drift #knowledge-management #documentation-maintenance #docs/solutions #ce-compound-refresh

Ready to run

npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-compound-refresh-bradliebs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ce-compound-refresh
Source: https://github.com/Bradliebs/VolumeTurtle/tree/main/.github/skills/ce-compound-refresh
Command: npx skills add https://github.com/Bradliebs/VolumeTurtle --skill ce-compound-refresh-bradliebs

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Maintains the quality of docs/solutions by reviewing existing learnings against the current codebase and refreshing or consolidating derived pattern docs to reflect new code, migrations, or refactors.

Core Features & Use Cases

Review learnings for drift against the codebase and flag outdated references.
Refresh, consolidate, replace, or delete docs to preserve accuracy and usability.
Generate a clear applicability and action report detailing Applied and Recommended changes.

Quick Start

Run ce-compound-refresh to assess learnings and refresh documentation against the current codebase.

Frequently Asked Questions about ce-compound-refresh

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

FAQPage Schema

How do I detect documentation drift against my current codebase?▼

Documentation drift detection is performed by reviewing learnings in docs/solutions/ to surface stale patterns and outdated code references. It compares documented learnings against the current codebase to identify missing consolidation opportunities and classify drift.

What is the best way to maintain accuracy of pattern docs after a refactor?▼

Maintaining pattern doc accuracy requires refreshing or consolidating derived documentation to reflect new code, migrations, or refactors. The process generates an applicability report detailing applied changes and recommended actions like updating references or replacing obsolete artifacts.

How do I consolidate outdated solution docs into canonical references?▼

Consolidating outdated solution docs involves reviewing existing learnings for drift, then replacing them with canonical successors or deleting obsolete artifacts. It classifies drift through evidence gathering and outputs a final report of recommended consolidation actions.

When should I use automated documentation maintenance for my codebase?▼

Automated documentation maintenance is needed when you have a docs/solutions/ directory containing accumulated learnings that must be reviewed against codebase changes. It preserves accuracy and usability by flagging outdated references and applying necessary updates after migrations or refactors.

Can I generate a report of recommended actions for stale documentation?▼

Generating a report of recommended actions for stale documentation is a core output of the drift review process. The final applicability report explicitly details both applied changes and recommended actions, covering reference updates, doc consolidation, and artifact deletion.

Does ce-compound-refresh require external dependencies to run?▼

The ce-compound-refresh process requires no external dependencies to run. It operates directly on your docs/solutions/ directory using built-in references and assets to classify drift and generate recommended maintenance actions.