docops/skills/gc/SKILL.md
Docops: garbage collection for resolved gaps, stale evidence, and redundant content. Scans conveyor-gaps.md, validates freshness, detects duplicates, archives cleaned items. Use when: 'gc docs', 'clean gaps', 'garbage collect documentation'.
npx skillsauth add murillodutt/cellm docops/skills/gcInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Garbage collection for resolved gaps, stale evidence, and redundant content.
conveyor-gaps.md by separating resolved gaps from active ones and archiving them.context_preflight mandatory before execution (flow='generic').done or resolved; never touch unresolved gaps.context_record_outcome after execution.context_preflight with flow='generic'; block execution if preflight fails.done/resolved) from active gaps in conveyor-gaps.md.## Resolved (Archive), keep last 20 for audit trail.context_record_outcome.done or resolveddata-ai
Prose override — temporarily disable quantization and respond in readable prose. Use when relational density matters, for safety-critical explanations, onboarding handoffs, or when token economy is not the priority.
development
Govern explicit weekly Super PRs or maintainer-requested PR merges. Evaluates a 10-criterion readiness checklist and performs governed merge only when a user-requested PR is READY. Never creates or keeps permanent PRs. Use when: 'pr-check', 'pr-merge', 'merge this PR safely', 'is PR ready', 'guard merge', or /sk-git delegates pr-merge.
data-ai
Operational surface for the compress-llm Layer-1 token I/O compressor. Enable, disable, switch mode, and inspect status without editing config files. Use when tuning compression pressure for the current session or project.
tools
Generate structured upstream feedback for the CELLM engineering team. Produces evidence-first Markdown at docs/evidence/<date>-cellm-feedback-*.md for bugs, anti-patterns, deprecation gaps, and harness surprises, with optional atom registration via knowledge_ops. Use when: 'feedback for CELLM', 'send to CELLM team', 'register this as atom', 'document this anti-pattern', 'report this bug upstream'. Trigger proactively on MCP schema/runtime mismatches, mechanical edit loops (>=3 sequential edits), short deprecation windows (<6 weeks), or reusable harness surprises. Do NOT trigger for routine feature work or project-local bugs.