github-repository-management

Manages GitHub repository collaboration workflows including issues, pull requests, reviews, and merge checks via GitHub MCP.

2.5k|524|Updated May 29, 2019
One-click install
npx skills add https://github.com/TencentBlueKing/bk-ci --skill github-repository-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-repository-management
Source: https://github.com/TencentBlueKing/bk-ci/tree/main/ai/skills/github-repository-management
Command: npx skills add https://github.com/TencentBlueKing/bk-ci --skill github-repository-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about github-repository-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub pull request from my local branch changes?

The workflow gathers your current branch name, target branch, local diff summary, and verification results, then drafts a PR title and body for your confirmation. Only after you approve does it call the GitHub MCP create_pull_request tool, defaulting to a draft PR if anything is unverified.

How do I avoid creating duplicate GitHub issues?

Before creating an issue, the workflow searches existing issues by title keywords, core module terms, and related closed issues using the GitHub MCP search_issues tool. It then drafts a title and body for your review before executing the write operation.

What is the difference between a PR comment and a review comment on GitHub?

Issue and PR general discussion uses add_issue_comment, while code review actions like approving, requesting changes, or resolving threads use pull_request_review_write. Sending review feedback as a plain comment breaks the review semantics, so the workflow selects the tool based on your intent.

When should I not use this GitHub collaboration workflow?

Do not use it when you only need to modify local code, discuss commit messages, or reorganize local git history, since those involve no GitHub remote actions. Deep correctness reviews of code should also go through a dedicated code review process instead.

What checks happen before merging a GitHub pull request?

Merging requires explicit user authorization, confirmation of the correct base branch, converged review conclusions, and no blocking check runs or conflicts. The workflow never guesses between merge, squash, or rebase unless the repository convention or user specifies it.