القائمة
Check whether a documentation topic is already covered on strapi/documentation: searches llms.txt, doc files, sidebars, and open GitHub PRs.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | exists |
| description | Check whether a documentation topic is already covered on strapi/documentation: searches llms.txt, doc files, sidebars, and open GitHub PRs. |
| argument-hint | [--no-log] <topic or keyword> |
| user-invocable | true |
$ARGUMENTS: a topic or keyword (e.g. MCP server, hasPublishedVersion, openapi.json route).
If no argument is provided and the conversation has context (e.g. a PR was just discussed), extract the relevant keywords from context.
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:research), write into that run's existing directory instead of creating a new one.
Read docusaurus/static/llms.txt at the repo root and find lines mentioning the topic (case-insensitive).
REPO_ROOT=$(git rev-parse --show-toplevel)
grep -i "<topic>" "$REPO_ROOT/docusaurus/static/llms.txt" | head -20
REPO_ROOT=$(git rev-parse --show-toplevel)
grep -rli "<topic>" "$REPO_ROOT/docusaurus/docs/cms" "$REPO_ROOT/docusaurus/docs/cloud" 2>/dev/null | head -20
For each match, optionally check when it was last touched:
git log -1 --format="%ai" -- "<path>"
REPO_ROOT=$(git rev-parse --show-toplevel)
grep -in "<topic>" "$REPO_ROOT/docusaurus/sidebars.js" | head -20
gh pr list --repo strapi/documentation --state all --search "<topic>" --limit 20 --json number,title,state,url
Bucket the PRs as: open (might be in progress), merged (might already cover the topic), closed-not-merged (abandoned attempts).
Report in this format:
Coverage check: "<query>"
Pages on docs.strapi.io that mention it:
- <path 1> (last updated YYYY-MM-DD, coverage: full | partial | mention)
- <path 2>
Sidebars referencing it:
- <entry>
PRs:
- Open: #<num> "<title>": <url>
- Merged: #<num> "<title>": <url>
- Closed: #<num> "<title>": <url>
Verdict: COVERED | PARTIAL | IN PROGRESS | NOT DOCUMENTED
Suggested next step: <e.g. "Run /inki:route with the related strapi/strapi PR" | "Run /inki:outline to start a new page" | none>
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.