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/labels.md
View on GitHub# Labels
Labels are repository-scoped objects with a name, a color, and an optional
description. Applying a label to an issue and creating a label are separate
operations, so list a repository's labels before using them rather than assuming
a name exists.
The `gh label` and `gh issue` commands act on the current repository; add
`--repo {owner}/{repo}` to target another one. `gh api` has no `--repo` flag: it
fills the `{owner}` and `{repo}` placeholders from the current repository, so set
`GH_REPO={owner}/{repo}` or write the values into the path when working elsewhere.
The GitHub MCP server's label tools require the non-default `labels` toolset and
cannot add or remove an individual label on an issue, so this reference uses the
`gh` CLI throughout.
## List Labels
`gh label list` returns only the first 30 labels. Always pass `--limit` when the
result decides whether a label exists, or the answer will be wrong on any
repository with a larger label set.
```bash
gh label list --limit 1000
```
Search names and descriptions, and return structured output:
```bash
gh label list --limit 1000 --search "triage"
gh label list --limit 1000 --json name,color,description --jq '.[] | "\(.name) (#\(.color))"'
```
Sort by name instead of creation order:
```bash
gh label list --limit 1000 --sort name --order asc
```
## Create Label
Only the name is required. Color is six hex characters **without** a leading `#`;
a random color is assigned when it is omitted. Description must be 100
characters or fewer.
```bash
gh label create "needs-triage" \
--color FBCA04 \
--description "Awaiting maintainer review"
```
Creating a label that already exists fails. Use `--force` to create it or update
its color and description if it is already there, which makes seeding a label set
repeatable:
```bash
gh label create "needs-triage" --color FBCA04 --force
```
## Rename or Recolor Label
Send only what changes. `--name` sets the new name.
```bash
gh label edit "needs-triage" --name "triage"
gh label edit "triage" --color D93F0B --description "Awaiting maintainer review"
```
## Delete Label
Deleting a label removes it from every issue and pull request that carries it.
`--yes` is required when running without a prompt. Delete a label only when
explicitly requested.
```bash
gh label delete "triage" --yes
```
## Copy Labels Between Repositories
Clones the source repository's labels into the current one, skipping names that
already exist. `--force` overwrites them instead.
```bash
gh label clone {owner}/{source-repo}
```
## View an Issue's Labels
```bash
gh issue view {issue_number} --json labels --jq '.labels[].name'
```
## Add Labels to an Issue
Adds to the labels already on the issue. Repeat the flag for several labels.
```bash
gh issue edit {issue_number} --add-label "bug" --add-label "needs-triage"
```
## Remove Labels from an Issue
```bash
gh issue edit {issue_number} --remove-label "needs-triage"
```
## Replace All Labels on an Issue
`gh issue edit` adds and removes but cannot replace the whole set. Use the API
endpoint for that: `PUT` drops the existing labels and sets the ones supplied.
```bash
gh api repos/{owner}/{repo}/issues/{issue_number}/labels \
-X PUT \
-f 'labels[]=bug'
```
## Remove All Labels from an Issue
Removes every label from the issue in one call. Remove all labels only when
explicitly requested. Read the current labels first, and prefer
`--remove-label` otherwise.
```bash
gh api repos/{owner}/{repo}/issues/{issue_number}/labels -X DELETE
```
## Default Labels
GitHub creates these labels in a new repository:
`accessibility`, `bug`, `documentation`, `duplicate`, `enhancement`,
`good first issue`, `help wanted`, `invalid`, `question`, `wontfix`.
Maintainers can rename or delete any of them, so check rather than assume. The
`isDefault` field separates them from labels the repository added:
```bash
gh label list --limit 1000 --json name,isDefault --jq '.[] | select(.isDefault | not) | .name'
```
## Usage Rules
- List the repository's labels before applying them, so the names used match the
repository's existing taxonomy. Pass `--limit` when doing so; the default of 30
silently hides the rest.
- Create a label explicitly, with a color and description, rather than relying on
a name appearing as a side effect of labelling an issue.
- Color is six hexadecimal characters with no leading `#`.
- Description must be 100 characters or fewer.
- Use `--add-label` and `--remove-label` to change part of an issue's labels.
They leave the other labels intact.
- Replace an issue's whole label set only when replacement is explicitly
requested. Read the current labels first, and prefer add and remove otherwise:
`PUT` discards every label not named in the call.
- Remove all of an issue's labels only when that is explicitly requested. Read
the current labels first: `DELETE` on the labels endpoint clears them all.
- Label names are matched case-insensitively and stored with the case given.
- Quote label names that contain spaces.
- Pass `--yes` to `gh label delete` when running without a prompt, and ask before
deleting: the label disappears from every issue that carries it.
- Prefer issue types over labels for categorization when the organization has
issue types configured.
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 |