القائمة
Given a strapi/strapi or strapi/cloud PR, identify which documentation pages and sections must be updated to cover the change.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | route |
| description | Given a strapi/strapi or strapi/cloud PR, identify which documentation pages and sections must be updated to cover the change. |
| argument-hint | [--no-log] <strapi/strapi or strapi/cloud PR: number or URL> |
| user-invocable | true |
Covers the two repos documented on docs.strapi.io: strapi/strapi (the CMS, routes to docs/cms/) and strapi/cloud (Strapi Cloud, routes to docs/cloud/).
$ARGUMENTS can be one of:
26847 (repo defaults to strapi/strapi; if ambiguous, ask)#26847https://github.com/strapi/strapi/pull/26847 or https://github.com/strapi/cloud/pull/123.../pull/26847/filesDetermine REPO (strapi/strapi or strapi/cloud) from the URL or an explicit owner/repo token; default to strapi/strapi for a bare number. Extract the trailing digits to obtain the PR number (regex [0-9]+$ after stripping a trailing /files, /commits, etc.). If no numeric PR ID can be extracted, report the error and stop. If REPO is neither strapi/strapi nor strapi/cloud, report that the repo is not documented on docs.strapi.io and stop.
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.
Fetch with gh pr view <num> --repo <REPO> --json title,body,files,labels.
Read ../../references/prompts/router.md. Use it as the system prompt over the PR data. Target docs/cms/ for a strapi/strapi PR and docs/cloud/ for a strapi/cloud PR.
<REPO> PR #<num>: <title>
Recommended docs targets:
- File: <doc path>
Section: <heading>
Action: <add | update | rework>
Template: <feature | plugin | guide | api | configuration | breaking-change>
Suggested branch name: <prefix>/<slug>
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.