What problem does it solve?
Committing and pushing code in the BK-CI repository involves conventions that are easy to get wrong: commit messages must follow issue-based formats, pushes should target a personal fork rather than the upstream repository, and unrelated or sensitive changes must not slip into a commit. This Skill enforces those rules so every commit and push is deliberate and correctly targeted.
Core Features & Use Cases
- Diff-based commit preview: Generates a short one-line commit summary from the actual current diff and shows it to the user for confirmation before running
git commit.
- Fork-first push strategy: Inspects remotes to distinguish the personal fork from the upstream repository, sets upstream tracking with
git push -u when needed, and refuses to push shared branches like master by default.
- Direct-push shortcut: When the user explicitly names an issue and says to push directly, it commits with the normalized message
<issue title> #<issue number> and pushes without a second confirmation.
- Use Case: After finishing changes on an issue branch, ask the assistant to commit and push; it reviews the diff, proposes
feat: add worktree skill #13062 added worker-skill file., waits for your approval, then pushes to your fork remote.
Quick Start
Ask the assistant to review my current changes, generate a commit message, and push the branch to my fork after I confirm.