ce:compound-refresh

Refresh learnings and pattern docs against the current codebase.

434|33|Updated Jul 27, 2025
One-click install
npx skills add https://github.com/udecode/kitcn --skill ce-compound-refresh-udecode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:compound-refresh
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/ce-compound-refresh
Command: npx skills add https://github.com/udecode/kitcn --skill ce-compound-refresh-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/ for accuracy, when a recently solved problem contradicts an existing learning, when pattern docs no longer reflect current code, or when multiple docs seem to cover the same topic and might benefit from consolidation.

Core Features & Use Cases

Maintain the quality of learnings and pattern docs by cross-checking with the codebase and applying updates, consolidations, replacements, or deletions as needed to reflect current reality. This workflow helps keep the docs aligned with code changes after refactors, migrations, or upgrades.

Quick Start

Use ce:compound-refresh to refresh learnings against the 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 keep my pattern docs aligned with the codebase after a major refactor?

Refreshing pattern docs after a refactor involves cross-checking them against the current codebase and applying updates, consolidations, or deletions to preserve documentation accuracy. It automates maintenance of learnings to reflect current reality.

What is the best way to maintain learnings docs when they drift from reality?

Docs maintenance for drifting learnings requires cross-checking them against the current codebase to produce a structured plan for updates, consolidations, replacements, or deletions. This workflow supports interactive or autofix modes to correct outdated information.

When should I consolidate or delete pattern docs in my knowledge base?

Consolidate or delete pattern docs when multiple entries cover the same topic or when a recently solved problem contradicts an existing learning. Cross-checking with the codebase identifies stale entries for replacement or deletion.

Does this docs maintenance workflow support interactive updates for codebase alignment?

Yes, codebase alignment supports both interactive and autofix workflows. It produces a structured plan for updates, consolidations, replacements, or deletions to maintain documentation accuracy after migrations or dependency upgrades.

Why does my retrieved learning feel outdated after a dependency upgrade?

Retrieved learnings feel outdated after dependency upgrades because pattern docs drift from reality over time. Cross-checking the docs against the current codebase identifies and corrects the stale information through structured updates.

Related Skills