Menu
Audit the documentation coverage of a Strapi feature or module: list what is documented vs missing.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Top-level review orchestrator: runs style-check, outline-check, outline-ux-analyzer, code-verify, coherence-check, and pitfalls-check on a file, directory, or PR.
Create a pull request on strapi/documentation following git-rules.md. Strict flat-text description, no headings, no test plan.
End-to-end documentation orchestrator: chains all four inki phases (research, write, review, submit) for a single subject. Gates between each phase by default; --non-interactive chains without pauses and runs a review-fix loop. The simplest way to document a subject from scratch.
Generate an outline for a new documentation page from a topic brief and the appropriate template.
Add a new entry to the known-pitfalls catalog that pitfalls-check audits against. Verifies the correct pattern against the Strapi source before adding, and confirms with the user. Use when you have found a documentation mistake worth catching automatically in future reviews.
Rewrite the title or description/body of one or more open PRs on strapi/documentation to match git-rules.md. Strict one-by-one confirmation, or auto-edit with --non-interactive.
Basé sur la classification professionnelle SOC
| name | coverage |
| description | Audit the documentation coverage of a Strapi feature or module: list what is documented vs missing. |
| argument-hint | [--no-log] <feature or module name> |
| user-invocable | true |
This skill compares a Strapi feature's public surface against the documentation. It needs access to the Strapi codebase, 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 Strapi feature name (e.g., "Users & Permissions plugin", "Document Service API"). Resolve to a set of source files using one of the sources listed in Prerequisites.
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:research), write into that run's existing directory instead of creating a new one.
List the public APIs, methods, hooks, configuration options, and CLI commands of the feature.
For each public element, search docusaurus/docs/cms and docusaurus/docs/cloud for mentions. Bucket as:
Feature: <name>
Documented (N/M):
- <element>: <doc path>
Partially documented:
- <element>: <doc path> (notes)
Undocumented:
- <element>: <suggested doc path>