Menu
Run deterministic style checks on a documentation file or directory, then layer AI judgment on top using the migrated style-checker prompt.
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 | style-check |
| description | Run deterministic style checks on a documentation file or directory, then layer AI judgment on top using the migrated style-checker prompt. |
| argument-hint | [--fix] [--no-log] <file or directory path> |
| user-invocable | true |
$ARGUMENTS is a relative path. If empty, use the diff between current branch and main:
git diff main...HEAD --name-only -- '*.md'
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:review), write into that run's existing directory instead of creating a new one.
The plugin ships a deterministic linter at claude-plugins/inki/scripts/style-lint.sh. It checks Markdown/MDX files against regex-based rules from the 12 Rules of Technical Writing (em dashes, casual language, simplification suggestions, bold prefixes that should be admonitions, etc.). Exit codes: 0 clean, 1 errors found, 2 warnings only.
Resolve the script path from the skill's location and run it on the target:
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]:-$0}")/../../scripts" && pwd)"
"$SCRIPT_DIR/style-lint.sh" <target>
If invoked from a Claude Code session, the equivalent is to read ../../scripts/style-lint.sh relative to this SKILL.md and execute it on the target.
Read ../../references/prompts/style-checker.md (relative to this SKILL.md location) and use it as the system prompt for an AI judgment pass over the target file's content.
Output findings in this format:
File: <path>
Deterministic issues:
- <line>: <issue>
AI-judged issues:
- <issue>: <suggested fix>
If invoked with --fix in $ARGUMENTS, apply non-controversial fixes (typos, formatting) and leave the rest as suggestions.