メニュー
Create, update, and manage GitHub issues using MCP tools. Use when: - Creating bug reports, feature requests, or task issues - Updating existing issues (labels, assignees, state) - Searching or filtering issues - Managing issue types, sub-issues, or dependencies
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | github-issues |
| description | Create, update, and manage GitHub issues using MCP tools. Use when: - Creating bug reports, feature requests, or task issues - Updating existing issues (labels, assignees, state) - Searching or filtering issues - Managing issue types, sub-issues, or dependencies |
Manage GitHub issues using MCP tools for reads and gh api for writes.
| Tool | Purpose |
|---|---|
mcp_github_issue_read | Read issue details, sub-issues, comments, labels |
mcp_github_list_issues | List and filter repository issues by state, labels, date |
mcp_github_search_issues | Search issues across repos using GitHub search syntax |
MCP does not currently support creating or updating issues. Use gh api:
| Operation | Command |
|---|---|
| Create issue | gh api repos/{owner}/{repo}/issues -X POST -f title=... -f body=... |
| Update issue | gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f title=... |
| Add comment | gh api repos/{owner}/{repo}/issues/{number}/comments -X POST -f body=... |
| Close issue | gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f state=closed |
| Set issue type | Include -f type=Bug in the create call (REST API only) |
gh api for writesgh api repos/{owner}/{repo}/issues \
-X POST \
-f title="Issue title" \
-f body="Issue body in markdown" \
-f type="Bug" \
--jq '{number, html_url}'
-f type="Bug" # Issue type (Bug, Feature, Task, Epic)
-f labels[]="bug" # Labels (repeat for multiple)
-f assignees[]="username" # Assignees
-f milestone=1 # Milestone number
Prefer issue types over labels for categorization. When issue types are available, use the type parameter instead of labels like bug or enhancement.
[Bug] when issue type is setBug Report:
## Description
[What's broken]
## Steps to Reproduce
1. ...
## Expected Behavior
[What should happen]
## Actual Behavior
[What happens instead]
Feature Request:
## Summary
[What and why]
## Motivation
[Why this matters]
## Proposed Solution
[How to implement]
## Acceptance Criteria
- [ ] ...
Task:
## Description
[What needs to be done]
## Deliverables
- [ ] ...
## Context
[Background information]
gh api repos/{owner}/{repo}/issues/{number} \
-X PATCH \
-f state=closed \
--jq '{number, html_url}'
Only include fields you want to change: title, body, state, labels, assignees, milestone.
| Label | Use For |
|---|---|
bug | Something isn't working |
enhancement | New feature or improvement |
documentation | Documentation updates |
high-priority | Urgent issues |
Related to #123Structured first-pass debugging for test failures, runtime errors, and unexpected behavior. USE FOR: test failure, assertion error, ImportError, traceback, debug failing test, fix broken test, diagnose error, runtime exception, mock error, config error. DO NOT USE FOR: complex multi-system design issues (escalate to @planner for re-planning).
Create, update, refactor, explain, or review Microsoft Agent Framework solutions. Use when working with the KB Agent (src/agent/) or any Microsoft Agent Framework code.
Patterns for adding governance, safety, and trust controls to AI agent systems using Microsoft Foundry and Azure API Management (APIM) AI Gateway. Use when: - Adding rate limiting, content safety, or jailbreak detection to agent traffic - Configuring APIM policies for token limits, throttling, or semantic caching - Leveraging Foundry tracing, evaluations, and agent monitoring - Implementing department-scoped access via JWT claims - Deciding what to handle at the platform layer vs. thin application code
Validates service boundary compliance in the KB Agent project. Use when working on cross-service imports, restructuring modules, or reviewing code that crosses service boundaries.
Performs comprehensive preflight validation of Bicep deployments to Azure. Use when: - Before deploying infrastructure to Azure - Reviewing or preparing Bicep files - Previewing what changes a deployment will make (what-if) - Verifying permissions are sufficient for deployment - Before running `azd -C infra/azure up`, `azd -C infra/azure provision`, or `az deployment` commands
Reviews Bicep modules, azure.yaml, and infrastructure changes for the KB Agent project. Checks naming, RBAC, module wiring, and doc sync. Use when working on infra/ or reviewing infrastructure PRs.