From docops
Docops: validate and maintain freshness status of code evidence files. Checks last_verified dates, transitions fresh/stale/expired, creates gaps for expired evidence. Use when: 'check freshness', 'stale evidence', 'validate dates'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/docops:freshnessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate and maintain freshness status of code evidence files.
Validate and maintain freshness status of code evidence files.
last_verified dates against freshness thresholds, and transition statuses accordingly.conveyor-gaps.md entries for expired evidence so drift is tracked.context_preflight optional; skip if unavailable, proceed regardless.--update, operate in report-only mode; with --update, apply status transitions.context_preflight with flow='generic'; proceed whether it succeeds or not.reference/code-evidence/.last_verified date:
stale_since field.last_verified) — add expired_since field, create GAP entry in conveyor-gaps.md.--update and human provides fresh date): remove stale_since/expired_since, update last_verified.npx claudepluginhub murillodutt/cellm --plugin docopsGenerates FPF evidence freshness reports identifying stale/expired items and supports refresh, deprecate, or waive actions for governance.
Audits project configuration and documentation for drift, staleness, and broken references. Scans CLAUDE.md files, configs, plugin manifests, and knowledge files.
Verifies factual accuracy of documents against codebase and git history: extracts claims, checks sources, corrects inaccuracies in place, adds summary. Targets reports/plans; auto-detects recent HTML or takes path.