Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From inki
Pushes the current branch in strapi/documentation to origin with branch name validation against git-rules.md conventions.
npx claudepluginhub strapi/documentation --plugin inkiHow this skill is triggered — by the user, by Claude, or both
Slash command
/inki:push (no arguments)(no arguments)The 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 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.
Pushes local Git commits to remote repositories, handling branch tracking, upstream setup, safe push patterns like force-with-lease, and verification. Useful after local commits when syncing to remote.
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).
Read and follow ../_shared/push-rules.md for: gathering state, safety checks, upstream status, showing the plan, and executing the push.
Check the branch name follows git-rules.md conventions:
/cms/, /cloud/, or /repo//doc/, /docs/, /feat/, /fix/, etc.)If non-compliant, warn the user but do not block (renaming an existing branch is disruptive). Suggest the correct prefix for future reference.
If on main, analyze recent changes to detect the area (cms/cloud/repo), then suggest:
Suggested:
git checkout -b /<prefix>/<description>