Menú
Push the current branch in strapi/documentation to origin. Validates branch name against git-rules.md conventions.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
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.
Basado en la clasificación ocupacional SOC
| name | push |
| description | Push the current branch in strapi/documentation to origin. Validates branch name against git-rules.md conventions. |
| argument-hint | (no arguments) |
| user-invocable | true |
Scope: designed for strapi/documentation (and its forks).
Read and follow ../_shared/push-rules.md for: gathering state, safety checks, upstream status, showing the plan, and executing the push.
Check the branch name follows git-rules.md conventions:
/cms/, /cloud/, or /repo//doc/, /docs/, /feat/, /fix/, etc.)If non-compliant, warn the user but do not block (renaming an existing branch is disruptive). Suggest the correct prefix for future reference.
If on main, analyze recent changes to detect the area (cms/cloud/repo), then suggest:
Suggested:
git checkout -b /<prefix>/<description>