Menu
Stage and commit documentation changes in strapi/documentation. Enforces git-rules.md, protected paths, and branch prefix detection.
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
| 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 |
Scope: designed for strapi/documentation (and its forks).
$ARGUMENTS: optional commit message. If not provided, one is generated from the diff.
Read and follow ../_shared/commit-rules.md for: gathering context, validating/generating the commit message, and executing the commit.
Before staging, check if any changed files are protected:
.github/workflows/* -- deployment infrastructuredocusaurus/docusaurus.config.js -- core site configdocusaurus/sidebars.js -- navigation structureIf protected files are present, require double confirmation before including them:
If declined, commit only the non-protected files.
After a successful commit, push automatically if on a working branch:
BRANCH=$(git branch --show-current)
$BRANCH is main or next: do NOT push. Warn the user.git push -u origin $BRANCHTop-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.