Menu
Create a new branch in strapi/documentation with auto-detected prefix (cms/, cloud/, repo/) based on the files that will be touched.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | branch |
| description | Create a new branch in strapi/documentation with auto-detected prefix (cms/, cloud/, repo/) based on the files that will be touched. |
| argument-hint | ["description of the work"] |
| user-invocable | true |
Scope: designed for strapi/documentation (and its forks).
$ARGUMENTS: description of the work (e.g., "add MCP server page", "fix deployment steps for cloud").
If no arguments provided, ask what the branch is for.
Ask which area the work will touch, or infer from the description:
docs/cms/ and/or static/ --> cms/docs/cloud/ and/or static/ --> cloud/repo/If ambiguous, default to repo/ and mention it.
From the description, generate a slug: lowercase, hyphens, no special characters, concise.
Format: <prefix>/<slug> (e.g., cms/add-mcp-server-page, cloud/fix-deployment-steps).
git checkout -b <branch-name>
Confirm with the branch name.