Stats
Actions
Tags
From docflow
Checks docflow setup and readiness status in one command. Returns a single status, reason, and next action when asked if docflow is configured or what to do next.
How this skill is triggered — by the user, by Claude, or both
Slash command
/docflow:checkThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Goal: answer "is this usable and what do I do next?" in one screen.
Goal: answer "is this usable and what do I do next?" in one screen.
bash scripts/docflow-check.sh --target <REPO ROOT>
If running from an installed plugin where scripts are not in the target repo, use the plugin script path.
| Status | Meaning | Next |
|---|---|---|
Ready | DocFlow is installed and validation is clean | Start normal docs work |
Needs setup | No meaningful docs or config detected | /docflow:init |
Needs adoption | Existing docs need docflow infrastructure | /docflow:adopt |
Needs repair | Generated helpers/guidance are missing | /docflow:repair |
Blocked | Validation found hard errors | /docflow:validate |
npx claudepluginhub medadembha/docflow --plugin docflowScans docs, config, changelog, and links to diagnose docflow setup. Recommends init, adopt, or repair based on findings.
Detects documentation drift, stale references, and cross-document inconsistencies in projects. Scans code-doc mismatches, broken links, outdated versions, and git staleness.
Audits documentation against source code using git-based staleness detection. Run with no args for smart check or specify a path. Supports full audit, auto-fix, and check-only modes.