ce:compound-refresh

Audit and refresh learnings and pattern docs against the current codebase.

Updated Sep 16, 2025
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill ce-compound-refresh-mukles
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:compound-refresh
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/ce-compound-refresh
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill ce-compound-refresh-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing them against the current codebase and applying updates, consolidations, or deletions to restore accuracy. Use after refactors, migrations, dependency upgrades, or when a learned pattern no longer matches the code. Also use when improving accuracy across multiple docs or when a recently solved problem contradicts existing guidance.

Core Features & Use Cases

  • Automates validation against code changes and migrations to detect drift.
  • Applies updates, consolidations, replacements, or deletions to keep docs aligned with code.
  • Generates an end-to-end maintenance report with two sections: Applied and Recommended.
  • Supports interactive mode (question-driven) or autofix mode for autonomous updates.
  • Triggers after refactors, migrations, or dependency upgrades, or when pattern/docs diverge from the current code.

Quick Start

Run ce:compound-refresh to audit and refresh learnings and pattern docs 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 refresh stale documentation after a code refactor or migration?

You can audit and refresh stale pattern documentation against the current codebase to detect drift after code refactors, applying updates, consolidations, or deletions to restore accuracy and keep docs aligned with recent changes.

What is documentation drift and how do I fix it?

Documentation drift occurs when learned patterns and guidance no longer match the current codebase due to migrations or dependency upgrades. You fix drift by auditing the docs against code changes and applying updates, replacements, or deletions to realign them.

Can I consolidate multiple docs covering the same topic automatically?

Yes, you can consolidate multiple docs covering the same topic using an autofix mode that applies safe updates, consolidations, or replacements autonomously, always producing a consolidated maintenance report for your records.

When should I audit my pattern docs against the codebase?

You should audit pattern docs after code migrations, refactors, or dependency upgrades, or when a recently solved problem contradicts existing guidance and when improving accuracy across multiple docs that have diverged from the current code.

Does updating outdated learnings require manual review?

Updating outdated learnings does not strictly require manual review because an autofix mode can autonomously apply safe updates, though an interactive review mode with questions is supported for manual validation of drift detection and changes.