OpenParable
Skip to content
← Back to skills

Code Verify

Testing & Quality
code-verify

Code Verify is an Agent Skill for testing & quality published in the strapi/documentation repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Verify code blocks in a documentation file: check syntax, references, and consistency with the underlying Strapi APIs.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/strapi/documentation/blob/HEAD/claude-plugins/inki/skills/code-verify/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/code-verify, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

/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):

  1. A local clone of strapi/strapi. Fastest and most reliable. Pass the path as input or ask the user.
  2. 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>