Help us improve
Share bugs, ideas, or general feedback.
From inki
Stage and commit documentation changes in strapi/documentation. Enforces git-rules.md, protected paths, and branch prefix detection.
npx claudepluginhub strapi/documentation --plugin inkiHow this skill is triggered — by the user, by Claude, or both
Slash command
/inki:commitThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Scope:** designed for strapi/documentation (and its forks).
Stages, commits, and optionally pushes local changes with a conventional commit message. Analyzes diffs, confirms with user. Automatically creates feature branches on protected branches.
Creates git commits with auto-generated conventional commit messages. Analyzes changes via git diff/status, checks branch protection, stages relevant files excluding secrets. Invoke via $commit or 'commit changes'.
Share bugs, ideas, or general feedback.
Scope: designed for strapi/documentation (and its forks).
$ARGUMENTS: optional commit message. If not provided, one is generated from the diff.
Read and follow ../_shared/commit-rules.md for: gathering context, validating/generating the commit message, and executing the commit.
Before staging, check if any changed files are protected:
.github/workflows/* -- deployment infrastructuredocusaurus/docusaurus.config.js -- core site configdocusaurus/sidebars.js -- navigation structureIf protected files are present, require double confirmation before including them:
If declined, commit only the non-protected files.
After a successful commit, push automatically if on a working branch:
BRANCH=$(git branch --show-current)
$BRANCH is main or next: do NOT push. Warn the user.git push -u origin $BRANCH