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.

2026-06-301.3k

strapi/documentation

Create a pull request on strapi/documentation following git-rules.md. Strict flat-text description, no headings, no test plan.

2026-06-181.3k

document

strapi/documentation

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.

2026-06-171.3k

outline

strapi/documentation

Generate an outline for a new documentation page from a topic brief and the appropriate template.

2026-06-161.3k

pitfalls-add

strapi/documentation

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.

2026-06-161.3k

pr-fix

strapi/documentation

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.

2026-06-161.3k

name	commit
description	Stage and commit documentation changes in strapi/documentation. Enforces git-rules.md, protected paths, and branch prefix detection.
argument-hint	["optional commit message"]
user-invocable	true

Documentation Commit

Scope: designed for strapi/documentation (and its forks).

Input

$ARGUMENTS: optional commit message. If not provided, one is generated from the diff.

Step 1: Apply shared commit rules

Read and follow ../_shared/commit-rules.md for: gathering context, validating/generating the commit message, and executing the commit.

Step 2: Protect infrastructure files

Before staging, check if any changed files are protected:

.github/workflows/* -- deployment infrastructure
docusaurus/docusaurus.config.js -- core site config
docusaurus/sidebars.js -- navigation structure

If protected files are present, require double confirmation before including them:

List each protected file with a warning
First confirmation: "Include these protected files?"
Second confirmation: Show the diff of each and ask: "Confirm you have reviewed these changes?"

If declined, commit only the non-protected files.

Step 3: Auto-push

After a successful commit, push automatically if on a working branch:

BRANCH=$(git branch --show-current)

If $BRANCH is main or next: do NOT push. Warn the user.
Otherwise: git push -u origin $BRANCH