What problem does it solve?
Coordinating GitHub collaboration—creating issues, drafting PRs, replying to reviews, and verifying merge readiness—requires juggling remote repository state with local code context, and mistakes like duplicate issues, wrong comment types, or premature merges are common.
Core Features & Use Cases
- Issue Management: Searches for duplicates before creating issues, drafts titles and bodies following bk-ci conventions (e.g.,
feat: ... prefixes), and updates or comments on existing issues.
- Pull Request Workflow: Combines local branch, diff, and test evidence with remote PR state to draft or create PRs, defaulting to draft PRs when requirements or verification are incomplete.
- Review and Merge Checks: Distinguishes issue comments from code review threads, replies to reviewers with the correct GitHub MCP tools, and verifies review status, check runs, and conflicts before merging.
- Use Case: After finishing a feature branch in the bk-ci repository, ask the assistant to check for existing PRs, draft a PR body with summary and test plan, and create a draft PR against
master only after you confirm the content.
Quick Start
Ask the assistant to check the current branch changes against TencentBlueKing/bk-ci and draft a pull request targeting master for your confirmation.