Menü
Top-level write orchestrator: outline a new page, get user approval, then draft from the outline.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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 | write |
| description | Top-level write orchestrator: outline a new page, get user approval, then draft from the outline. |
| argument-hint | [--non-interactive] [--no-log] <topic brief or path to a brief file> |
| user-invocable | true |
If $ARGUMENTS contains --help or -h, print usage and stop, per ../../references/help.md. Do not run the workflow.
Otherwise, from $ARGUMENTS, detect the autonomy flag anywhere in the list: --non-interactive (canonical), aliases --auto-approve, --auto, --yes, -y, --no-questions-asked (all equivalent). If present, set AUTO=true and remove the flag. What remains is the topic brief (text or path to a .md file).
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:document), write into that run's existing directory instead of creating a new one.
AUTO=false, default)/inki:outline $ARGUMENTS. Wait for user approval inside that sub-skill./inki:draft <outline-path>.If the user rejects the outline, stop. Do not draft.
AUTO=true)/inki:outline --non-interactive $ARGUMENTS. The outline is generated and saved without an approval gate./inki:draft <outline-path> on the resulting outline.In auto mode, the user sees the outline and the draft only after both are produced. They can still discard the outputs if they don't fit; nothing is committed automatically. --non-interactive here means "don't pause between outline and draft," not "trust the output blindly."
/inki:submit for that.