Stats
Actions
Tags
From inki
Given a Strapi PR number or URL, identifies which documentation pages and sections need updates to cover the code change.
How this skill is triggered — by the user, by Claude, or both
Slash command
/inki:route <strapi/strapi PR number or URL><strapi/strapi PR number or URL>The summary Claude sees in its skill listing — used to decide when to auto-load this skill
`$ARGUMENTS` can be one of:
$ARGUMENTS can be one of:
26847#26847https://github.com/strapi/strapi/pull/26847https://github.com/strapi/strapi/pull/26847/filesExtract the trailing digits to obtain the PR number. A simple regex [0-9]+$ (after stripping a trailing /files, /commits, etc. if present) is sufficient. If no numeric PR ID can be extracted, report the error and stop.
Fetch with gh pr view <num> --repo strapi/strapi --json title,body,files,labels.
Read ../../references/prompts/router.md. Use it as the system prompt over the PR data.
strapi/strapi 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>
npx claudepluginhub strapi/documentation --plugin inkiCreates, updates descriptions, and adds comments to GitHub pull requests using file-based drafts for safety, emphasizing material impact and reviewer-friendly communication.
Drafts conventional commit PR titles and Shopware 5-section descriptions for core PRs targeting trunk. Analyzes branch against trunk, uses session context, asks for missing info.