Stats
Actions
Tags
From inki
Runs deterministic regex-based style checks on Markdown/MDX documentation files, then layers AI judgment for deeper issues. Useful for enforcing doc style guides.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inki:style-check <file or directory path><file or directory path>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
`$ARGUMENTS` is a relative path. If empty, use the diff between current branch and `main`:
$ARGUMENTS is a relative path. If empty, use the diff between current branch and main:
git diff main...HEAD --name-only -- '*.md'
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.
npx claudepluginhub strapi/documentation --plugin inkiOrchestrates six sub-skills to review documentation files, directories, or PRs: style, outline, UX, code verification, coherence, and pitfalls.
Proofreads Markdown documents for style violations per guidelines, detects issues excluding code/URLs/frontmatter, proposes fixes, and applies user-approved edits via interactive prompts.
Updates READMEs, ADRs, docstrings, and docs after code changes using consolidation detection, slop scanning, accuracy verification, and quality gates.