ce:compound-refresh

Refresh stale docs under docs/solutions/ after codebase changes.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-compound-refresh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce:compound-refresh
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/ce-compound-refresh
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill ce-compound-refresh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Docs in docs/solutions/ drift over time as refactors migrations upgrades and fixes introduce new patterns, leaving learners with outdated or misleading guidance. This Skill maintains doc quality by reviewing each learning and pattern against the current codebase, making it easy to spot stale references and consolidate redundant notes.

Core Features & Use Cases

  • Automated mode detection: Detects autofix mode from arguments to either ask for clarifications interactively or run deterministic bulk updates without interruption.
  • Evidence-driven refresh rules: Provides detailed guidance on Keep/Update/Consolidate/Replace/Delete decisions, ensuring your documentation matches current implementations.
  • Autofix reporting: Applies safe updates automatically, marks ambiguous cases as stale, and produces a clear Applied vs Recommended summary for each run.

Quick Start

After a refactor run ce:compound-refresh to reassess docs/solutions accuracy.

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 documentation synced with code after a refactor?

To keep docs synced with code after a refactor, run a refresh workflow that reviews pattern docs against the current codebase, applies safe updates automatically, and marks ambiguous references as stale.

What is the best way to update stale pattern docs in docs/solutions?

Updating stale pattern docs involves evaluating each learning against the current codebase using evidence-driven rules to Keep, Update, Consolidate, Replace, or Delete outdated guidance.

How does autofix mode work for documentation maintenance?

Autofix mode for documentation maintenance applies deterministic updates automatically without interruption, marks uncertain cases as stale, and generates an Applied versus Recommended summary report for each run.

When should I refresh my codebase learnings and pattern docs?

You should refresh codebase learnings and pattern docs after migrations, dependency updates, refactors, or when retrieved learnings contradict new fixes implemented in the codebase.

Can I run bulk documentation updates without interactive prompts?

Yes, you can run bulk documentation updates without interactive prompts by enabling autofix mode, which detects arguments to execute deterministic updates continuously and skip clarifications.