From wf-rituals
Mechanical checks over the project's narrative documentation tree (`docs/`). Reports broken code references, removed-feature docs, orphan files, and documentation TODOs. Reports only — never rewrites prose. Use before opening a PR that touches code with documentation impact, or as a periodic doc-hygiene pass.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wf-rituals:wf-doc-lintThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A non-interactive lint over a project's narrative docs. Surfaces drift between docs and code without rewriting anything. The output is a report; what to do about each finding is the human's call.
A non-interactive lint over a project's narrative docs. Surfaces drift between docs and code without rewriting anything. The output is a report; what to do about each finding is the human's call.
This skill is intentionally narrow: structural correctness of narrative documentation, mechanical checks a pipeline can run. It does not judge content quality, alignment of prose with code semantics, or doc tier. Those need human or AI prose work, not a lint.
Walk every doc in docs/ (or whatever the project's docs root is). Find references to code symbols (function names, class names, file paths, route paths, config keys). For each reference:
Report broken references with the doc's path:line and the missing symbol.
If a doc describes a feature whose code has been removed, flag it. Heuristic: docs that are the sole remaining reference to a symbol-like token, where the token doesn't appear anywhere in source, are candidates. False positives are tolerable; the reviewer decides whether the doc should be archived or rewritten.
Docs with no inbound links from any other doc, README, or code file. They might be alive (a top-level overview that everything links to externally) or dead (a stale draft someone forgot to archive). Flag for human inspection — don't delete.
TODO, FIXME, XXX, or similar markers anywhere under docs/. List them with path:line. Most projects accumulate these; the lint just makes them visible so they can be triaged or grandfathered explicitly.
docs/. Some projects use documentation/, book/, or a flat top-level. Read README.md or look for the obvious folder.# Doc lint report — <YYYY-MM-DD>
**Scope:** full | scoped (<N> changed files)
**Docs root:** docs/
## Broken code references
- `docs/architecture/api.md:42` — references `OldHandler.serve()`; symbol not found in source.
- `docs/guides/cli.md:7` — references `--legacy-flag`; flag removed in commit <SHA>.
## Removed-feature docs
- `docs/features/x-mode.md` — describes "X mode"; no source reference found.
## Orphan files
- `docs/scratch/notes-2024.md` — no inbound links; last modified <date>.
## Documentation TODOs
- `docs/getting-started.md:18` — `TODO: rewrite once auth lands`
- `docs/api.md:104` — `FIXME: example may be stale`
## Summary
- <N> findings: <breakdown>
- <one-line takeaway>
If nothing is found, the report has empty sections and the summary is a single line: "No findings — <N> docs checked."
docs/ — including for "obvious" mechanical fixes.path:line references. A finding without a location is unactionable.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub 23min/ai-workflow-rituals --plugin wf-rituals