docops/skills/deprecate/SKILL.md
Docops: mark documentation for deprecation with configurable grace period before archival. Adds deprecation banner, updates references, schedules archive date. Use when: 'deprecate this doc', 'mark for removal'.
npx skillsauth add murillodutt/cellm docops/skills/deprecateInstall 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.
Mark documentation for deprecation with grace period before archival.
context_preflight mandatory before execution (flow='generic').--days N. Grace periods: SPEC 30d, REF 30d, HOWTO 14d, RUNBOOK 7d, ADR never.context_record_outcome after execution.context_preflight with flow='generic'; block execution if preflight fails.--days N).> [!WARNING] deprecation banner at top of file.status: deprecated, deprecated_on, deprecated_by, deprecation_reason, archive_on, replacement.archive_on: today + grace period (minimum 7 days).[DEPRECATED] marker next to links pointing to this file.context_record_outcome.> [!WARNING] at top[DEPRECATED]data-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.