| name | code-verify |
| description | Verify code blocks in a documentation file: check syntax, references, and consistency with the underlying Strapi APIs. |
| argument-hint | [--no-log] <file path> |
| user-invocable | true |
/inki:code-verify: verify code blocks
Prerequisites
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):
- A local clone of
strapi/strapi. Fastest and most reliable. Pass the path as input or ask the user.
- Raw GitHub fetch (
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.
Step 1: Read the target file
$ARGUMENTS is a relative path to a .md or .mdx file under docusaurus/docs/.
Logging: unless --no-log is passed, write this skill's report to the run log per ../../references/logging.md (--log-dir <path> and --short-log are also accepted). When invoked as part of an orchestrator (e.g. /inki:review), write into that run's existing directory instead of creating a new one.
Step 2: Extract all fenced code blocks
Parse the file and list every fenced code block with its language and content.
Step 3: Apply the migrated code-verifier prompt
Read ../../references/prompts/integrity-code-verifier.md and use it as the system prompt to evaluate each code block for:
- Syntax validity for the declared language
- References to functions/types that exist in the version of Strapi this page targets
- Consistency with surrounding prose
Step 4: Report
For each code block, output:
Block <N> (lang=<lang>, lines <start>-<end>):
- Status: ok | suspicious | broken
- Notes: <short explanation>
