github/awesome-copilot / skills/github-issues
github-issues
UnverifiedCreate, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, manage repository labels, set issue fields (dates, priority, custom fields), set issue types, manage issue workflows, link issues, add dependencies, or track blocked-by/blocking relationships. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", "set the priority", "set the start date", "create a label", "rename a label", "list repo labels", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management task.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.0 KB |
| references/dependencies.md | markdown | 1.8 KB |
| references/images.md | markdown | 4.7 KB |
| references/issue-fields.md | markdown | 7.6 KB |
| references/issue-types.md | markdown | 1.7 KB |
| references/labels.md | markdown | 5.2 KB |
| references/milestones.md | markdown | 2.4 KB |
| references/projects.md | markdown | 8.4 KB |
| references/search.md | markdown | 7.1 KB |
| references/sub-issues.md | markdown | 3.6 KB |
| references/templates.md | markdown | 1.4 KB |
references/milestones.md
View on GitHub# Milestones
Use milestones to group related issues into a deliverable unit of work.
Milestones can be read and managed through the GitHub REST API.
## List Milestones
```bash
gh api "repos/{owner}/{repo}/milestones?state=all&per_page=100" \
--paginate \
--jq '.[] | {number, title, state, open_issues, closed_issues, due_on}'
```
## Get Milestone
```bash
gh api repos/{owner}/{repo}/milestones/{milestone_number}
```
## Create Milestone
```bash
gh api repos/{owner}/{repo}/milestones \
-X POST \
-f title="Milestone title" \
-f description="Milestone description"
```
Optional due date:
```bash
gh api repos/{owner}/{repo}/milestones \
-X POST \
-f title="Milestone title" \
-f description="Milestone description" \
-f due_on="2026-09-01T00:00:00Z"
```
## Update Milestone
```bash
gh api repos/{owner}/{repo}/milestones/{milestone_number} \
-X PATCH \
-f title="Updated title" \
-f description="Updated description"
```
## Close Milestone
```bash
gh api repos/{owner}/{repo}/milestones/{milestone_number} \
-X PATCH \
-f state=closed
```
## Reopen Milestone
```bash
gh api repos/{owner}/{repo}/milestones/{milestone_number} \
-X PATCH \
-f state=open
```
## List Issues in Milestone
Use the milestone number, not the milestone title.
```bash
gh api "repos/{owner}/{repo}/issues?milestone={milestone_number}&state=all&per_page=100" \
--paginate \
--jq '.[] | select(.pull_request == null) | {number, title, state}'
```
The Issues REST endpoint can also return pull requests, so exclude entries
containing `pull_request` when the caller specifically requests milestone issues.
## Assign Issue to Milestone
```bash
gh api repos/{owner}/{repo}/issues/{issue_number} \
-X PATCH \
-F milestone={milestone_number}
```
## Remove Issue from Milestone
```bash
gh api repos/{owner}/{repo}/issues/{issue_number} \
-X PATCH \
-F milestone=null
```
## Delete Milestone
Delete a milestone only when explicitly requested.
```bash
gh api repos/{owner}/{repo}/milestones/{milestone_number} \
-X DELETE
```
## Usage Rules
- Use milestone numbers for API operations.
- A milestone groups work; it does not define issue execution order.
- Use native issue dependencies for execution ordering.
- Do not infer dependencies merely because issues belong to the same milestone.
- Listing a milestone for an automated workflow should include all open and
closed issues unless the caller explicitly requests otherwise.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |