ce-compound-refresh

Audit docs/solutions against the codebase and apply evidence-based updates.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/KingInYellows/yellow-plugins --skill ce-compound-refresh-kinginyellows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-compound-refresh
Source: https://github.com/KingInYellows/yellow-plugins/tree/main/RESEARCH/upstream-snapshots/e5b397c9d1883354f03e338dd00f98be3da39f9f/plugins/compound-engineering/skills/ce-compound-refresh
Command: npx skills add https://github.com/KingInYellows/yellow-plugins --skill ce-compound-refresh-kinginyellows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill helps maintain the quality and relevance of docs/solutions by auditing learnings and pattern docs against the active codebase, then refreshing or consolidating content as needed.

Core Features & Use Cases

  • Audit learnings and pattern docs against the current codebase to identify drift.
  • Propose and apply updates, consolidations, replacements, or deletions to keep documentation aligned.
  • Generate a structured maintenance report with actions taken and rationale for future improvements.

Quick Start

Run ce-compound-refresh to audit and refresh stale docs in docs/solutions against the latest 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 between pattern docs and the current codebase?

To detect documentation drift, you can audit learnings and pattern docs against the active codebase. This identifies inconsistencies where documentation no longer reflects the current implementation.

What is the best way to consolidate stale solutions documentation?

The best way to consolidate stale solutions documentation is to audit it against the codebase, then apply updates, replacements, or deletions based on evidence to ensure alignment.

Can I target a specific scope when refreshing outdated technical docs?

Yes, you can refresh outdated technical docs within a focused, batch, or broad scope. This allows you to apply targeted updates or broad consolidations depending on the drift severity.

How do I generate a maintenance report for documentation updates?

You generate a maintenance report by auditing docs against the codebase and applying changes. The resulting structured report details applied actions, recommendations, rationale, and missing evidence.

When should I avoid automated documentation refresh?

You should avoid automated documentation refresh when there is missing evidence to support updates. The process relies on concrete codebase evidence to propose replacements or consolidations safely.