clean-docs

Solid

Clean up the repository's docs, comments, rules, and tests as a CAFleet team of disjoint-slice scanner members gated by a reviewer — exactly one workflow per run. Use the residue workflow when the user asks to clean up historical narration or historical residue, remove deprecation notes / "this replaces X" / "renamed from Y" / "previously … now …" prose, drop design-number provenance citations, or delete removal-sentinel tests. Use the affirmative workflow when the user asks to run an affirmative-writing sweep, fix prohibition-only rule sections, pair prohibitions with affirmatives, remove meaningless fallbacks, or make code fail fast. Use the simplification workflow when the user asks to simplify the docs or comments, tighten verbose prose, de-duplicate documentation, or remove redundant comments. Nothing is applied before the reviewer approves the merged run artifact. Members load this skill by its name clean-docs via their backend's skill-loader.

AI & Automation 43 stars 4 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%
55
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Clean-Docs Skill (CAFleet-orchestrated) One skill, three workflows — **residue**, **affirmative**, **simplification** — run as the same CAFleet team shape over the same per-run process. This page is the dispatcher and the single home of the **shared orchestration spine**; each workflow body (`<workflow>/<workflow>.md`) carries only its own trigger scenario, scan mechanics, artifact spec, and guarantees, citing the spine here rather than restating it. ## Required reading Identify your coding agent first — a member's spawn prompt names it on the `CODING AGENT:` line; the Director (main session) uses its own identity — then Read your overlay and **resolve** it before your first action. **Load-bearing — Read in order before acting:** | # | Read | What you lose if you skip it | |---|------|------------------------------| | 1 | your overlay [`../../../skills/cafleet/reference/coding-agent/<name>-overlay.md`](../../../skills/cafleet/reference/coding-agent/) — read **and resolve** it (see *Resolve your overlay* in the cafleet `SKILL.md`) | you emit a literal `{monitor_model}` / `{reviewer_model}` / `{skill_loader}` / `{decision_surface}`, guess a wrong value, or ignore a backend note | | 2 | the `cafleet` skill's [`reference/base-dir.md`](../../../skills/cafleet/reference/base-dir.md) | the task-scope BASE resolution, the no-bypass write protocol, and the `<unset>` contract — you mis-root run artifacts or fall back to `/tmp` | | 3 | the `cafleet-design-doc` skill's [`reference...

Details

Author
himkt
Repository
himkt/cafleet
Created
4 months ago
Last Updated
2 days ago
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

cafleet-design-doc

Use when the user asks to create a design doc, design document, specification, or technical spec (create workflow → Director/Drafter/Reviewer team); to validate, review, or interview an existing design doc through multi-round Q&A (interview workflow); or to implement or execute a design doc (execute workflow → TDD team). Also the standardized format spec — consult the template and guidelines when editing a design doc. Always invoke this skill and route into the matching workflow, orchestrated as a CAFleet team. Teammates in member teams load this skill by its name cafleet-design-doc via their backend's skill-loader.

43 Updated 2 days ago
himkt
Code & Development Featured

docs-corpus-audit

Use this skill to run a holistic regrounding pass on the entire microsoft/apm documentation corpus against current source code, page-by-page, and emit surgical fixes for stale claims. Activate when the maintainer wants a WHOLE-CORPUS audit (not per-PR review) -- typical triggers include "audit the docs", "reground the corpus", "check every page against code", "pre-release docs sweep", "the docs have drifted everywhere", or "we just reshaped the TOC, find dead links". Wave-batched and S7-verified; scales to the full ~112-page corpus in ~10 minutes wall-time. This is a SIBLING to docs-sync, not a replacement: docs-sync is per-PR (triggered by a diff); this skill is per-corpus (triggered by a maintainer ask). They share agent personas, schemas, and the docs index, but their triggers MUST NOT collide. Does NOT auto-merge, does NOT push without maintainer review, and does NOT replace per-PR drift detection.

3,379 Updated yesterday
microsoft
AI & Automation Listed

clarify-docs

Hygiene phase skill. Fix doc/code drift, broken refs, stale ADRs, missing glossary terms, failed example commands. Docs-only PR, ≤3 files, ≤100 lines diff. Run via bookie create --kind task --class hygiene --title 'clarify-docs: <observation>'.

0 Updated yesterday
a-canary