Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From inki
Validates branch name conventions and pushes the current branch to origin for the strapi/documentation repository. Checks prefixes and suggests branch creation when on main.
How 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).
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>
npx claudepluginhub strapi/documentation --plugin inkiCreates a new branch in strapi/documentation with auto-detected prefix (cms/, cloud/, repo/) based on the files to be touched. Useful for maintaining consistent branch naming across documentation areas.
Generates and validates Git branch names per the Conventional Branch specification (feature/, bugfix/, hotfix/, release/, chore/). Guides users through branch type selection, description formatting, name validation, and base branch detection.
Commits and pushes current changes on a single branch using Conventional Commit messages. Handles staging, message building, and push for quick handoffs.