Help us improve
Share bugs, ideas, or general feedback.
From inki
Check a documentation file for cross-page coherence: terminology, links, and consistency with related pages.
npx claudepluginhub strapi/documentation --plugin inkiHow this skill is triggered — by the user, by Claude, or both
Slash command
/inki:coherence-check <file path><file path>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
For the target file, find related pages by:
Reviews documentation for data inconsistencies, broken references, typos, and unclear terminology. Use before publishing or committing to catch cross-file quality issues.
Validates project documentation: lints formatting and naming, checks broken/orphan links, verifies glossary terms and synonyms, detects contradictions/gaps, audits completeness via /doc:lint, /doc:links, etc.
Validates documentation references including file paths, links, line numbers, and code examples using Read, Grep, Glob. Ensures docs accuracy across projects.
Share bugs, ideas, or general feedback.
For the target file, find related pages by:
docusaurus/static/llms.txt for entries on the same topicRead ../../references/prompts/integrity-coherence-checker.md and use it as the system prompt. Compare the target against each related page.
Target: <path>
Related pages compared: <list>
Coherence issues:
- <description>: <where it conflicts>