Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From inki
Verifies code blocks in Strapi documentation by checking syntax, references, and consistency against the actual Strapi codebase.
npx claudepluginhub strapi/documentation --plugin inkiHow this skill is triggered — by the user, by Claude, or both
Slash command
/inki:code-verify <file path><file path>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill compares the code blocks in a documentation page against the actual Strapi codebase. It needs access to the source, in one of these forms (by preference):
Audits a documentation file against a known-pitfalls catalog of common mistakes, outdated patterns, and deprecated APIs, reporting matches per entry.
Verifies documentation code examples match codebase: class names, method signatures, namespaces, imports, parameters. Uses grep/bash; ideal for PHP/Laravel projects.
Audits repository documentation for drift, stale statements, broken references, and README mismatches before corrective PRs.
Share bugs, ideas, or general feedback.
This skill compares the code blocks in a documentation page against the actual Strapi codebase. It needs access to the source, in one of these forms (by preference):
strapi/strapi. Fastest and most reliable. Pass the path as input or ask the user.https://raw.githubusercontent.com/strapi/strapi/develop/<path>). Works without a local clone but rate-limited and slower.If neither is available, ask the user for a path or fall back to GitHub fetches.
$ARGUMENTS is a relative path to a .md or .mdx file under docusaurus/docs/.
Parse the file and list every fenced code block with its language and content.
Read ../../references/prompts/integrity-code-verifier.md and use it as the system prompt to evaluate each code block for:
For each code block, output:
Block <N> (lang=<lang>, lines <start>-<end>):
- Status: ok | suspicious | broken
- Notes: <short explanation>