What problem does it solve?
When working on the bk-ci repository's master branch, developers need a disciplined way to spin up isolated work environments tied to GitHub Issues without manually juggling branch naming, worktree creation, IDE config syncing, and jOOQ code generation.
Core Features & Use Cases
- Issue-Driven Branching: Links work to an existing GitHub Issue or creates a new one on TencentBlueKing/bk-ci via GitHub MCP, then derives a conventional branch name like
feat-knowledge-13058.
- Automated Worktree Setup: Cross-platform scripts (PowerShell and Bash) create a new branch based on
origin/master together with a git worktree, then sync .idea and .cursor configs into it.
- Environment Bootstrap: After worktree creation, the scripts run all jOOQ generation Gradle tasks in
src/backend/ci and open the new worktree in a new Cursor window.
- Use Case: A developer on master is asked to fix a pipeline bug. The skill confirms the issue, creates branch
bug-12994 with a matching worktree, syncs IDE settings, runs jOOQ generation, and opens a fresh Cursor window ready for coding.
Quick Start
Ask the assistant to create a worktree for GitHub Issue 12994 following the github-worktree workflow while on the master branch.