inki

Plugin inki from marketplace strapi-documentation in strapi/documentation. Commands read from the repo's manifest — today.

Skills (23)

• branch

  Create a new branch in strapi/documentation with auto-detected prefix (cms/, cloud/, repo/) based on the files that will be touched.

• code-verify

  Verify code blocks in a documentation file: check syntax, references, and consistency with the underlying Strapi APIs.

• coherence-check

  Check a documentation file for cross-page coherence: terminology, links, and consistency with related pages.

• commit

  Stage and commit documentation changes in strapi/documentation. Enforces git-rules.md, protected paths, and branch prefix detection.

• coverage

  Audit the documentation coverage of a Strapi feature or module: list what is documented vs missing.

• document

  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.

• draft

  Draft a documentation page from an approved outline, the matching template, and the relevant authoring guide.

• exists

  Check whether a documentation topic is already covered on strapi/documentation: searches llms.txt, doc files, sidebars, and open GitHub PRs.

• inki-interactive-demo

  Create or update an interactive demo (the clickable product tours that replaced Guideflow) from a plain-text description of its steps: finds the UI elements in a running Strapi demo app, writes the YAML scenario, captures it and checks the result.

• outline-check

  Check the structural outline of a documentation page: heading hierarchy, section order, completeness against the template.

• outline-ux-analyzer

  Analyze the pedagogical UX of a documentation outline: progression from beginner to advanced, signposting, and reading flow.

• outline

  Generate an outline for a new documentation page from a topic brief and the appropriate template.

• pitfalls-add

  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.

• pitfalls-check

  Audit a documentation file against the known-pitfalls list: common mistakes, outdated patterns, deprecated APIs.

• pr-fix

  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.

• pr

  Create a pull request on strapi/documentation following git-rules.md. Strict flat-text description, no headings, no test plan.

• push

  Push the current branch in strapi/documentation to origin. Validates branch name against git-rules.md conventions.

• research

  Top-level research orchestrator: combines exists, route, and coverage to give a complete picture before writing.

• review

  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.

• route

  Given a strapi/strapi or strapi/cloud PR, identify which documentation pages and sections must be updated to cover the change.

• style-check

  Run deterministic style checks on a documentation file or directory, then layer AI judgment on top using the migrated style-checker prompt.

• submit

  Top-level orchestrator: branch (if needed), commit, push, then open a PR. Each step asks for confirmation before continuing, unless --non-interactive is passed.

• write

  Top-level write orchestrator: outline a new page, get user approval, then draft from the outline.

Subagents (6)

• code-verifier

  Read-only verifier of code blocks in a documentation page against the real Strapi codebase. Checks syntax, API references, and consistency with surrounding prose. Returns only a per-block findings report. Use when verifying that code samples in a docs page are correct and current.

• coherence-checker

  Read-only cross-page coherence reviewer. Checks one documentation page against related pages for consistent terminology, working links, and non-conflicting instructions. Returns only a findings report. Use when verifying a docs page agrees with the rest of the docs set.

• outline-checker

  Read-only structural reviewer for a single documentation page. Compares the page's heading hierarchy and section order against the matching template. Returns only a findings report. Use when auditing the structure of a docs page.

• pitfalls-checker

  Read-only auditor that matches a documentation page against the known-pitfalls catalog of common mistakes, outdated patterns, and deprecated APIs. Returns only a findings report. Use when checking a docs page for documented hallucination patterns.

• style-checker

  Read-only style reviewer for a single documentation file. Runs the deterministic style-lint script, then layers AI judgment from the style-checker prompt. Returns only a findings report. Use when reviewing the writing style of a docs page.

• ux-analyzer

  Read-only pedagogical UX reviewer for a single documentation page. Evaluates progression from beginner to advanced, signposting, and reading flow. Returns only a findings report with a UX score. Use when auditing the learning experience of a docs page.