Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From inki
Creates a new git branch in Strapi's documentation repo with auto-detected prefix (cms/, cloud/, repo/) based on the files touched. Useful for structured branch naming.
npx claudepluginhub strapi/documentation --plugin inkiHow this skill is triggered — by the user, by Claude, or both
Slash command
/inki:branchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Scope:** designed for strapi/documentation (and its forks).
Creates git branches following Sentry naming conventions by analyzing changes and classifying branch types. Useful for standardizing branch creation.
Creates git branches following Sentry naming conventions. Automatically determines branch type and description from arguments or local diff. Useful when starting new work.
Share bugs, ideas, or general feedback.
Scope: designed for strapi/documentation (and its forks).
$ARGUMENTS: description of the work (e.g., "add MCP server page", "fix deployment steps for cloud").
If no arguments provided, ask what the branch is for.
Ask which area the work will touch, or infer from the description:
docs/cms/ and/or static/ --> cms/docs/cloud/ and/or static/ --> cloud/repo/If ambiguous, default to repo/ and mention it.
From the description, generate a slug: lowercase, hyphens, no special characters, concise.
Format: <prefix>/<slug> (e.g., cms/add-mcp-server-page, cloud/fix-deployment-steps).
git checkout -b <branch-name>
Confirm with the branch name.