github-issues
installsforks
How to install github-issues?
github/awesome-copilot/github-issues
$npx -y skills add github/awesome-copilot --skill github-issuesCreate, 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, set issue fields (dates, priority, custom fields), set issue types, manage is
SKILL.md
| 1 | # GitHub Issues |
| 2 | |
| 3 | Manage GitHub issues using the `@modelcontextprotocol/server-github` MCP server. |
| 4 | |
| 5 | ## Available Tools |
| 6 | |
| 7 | ### MCP Tools (read operations) |
| 8 | |
| 9 | | Tool | Purpose | |
| 10 | |------|---------| |
| 11 | | `mcp__github__issue_read` | Read issue details, sub-issues, comments, labels (methods: get, get_comments, get_sub_issues, get_labels) | |
| 12 | | `mcp__github__list_issues` | List and filter repository issues by state, labels, date | |
| 13 | | `mcp__github__search_issues` | Search issues across repos using GitHub search syntax | |
| 14 | | `mcp__github__projects_list` | List projects, project fields, project items, status updates | |
| 15 | | `mcp__github__projects_get` | Get details of a project, field, item, or status update | |
| 16 | | `mcp__github__projects_write` | Add/update/delete project items, create status updates | |
| 17 | |
| 18 | ### CLI / REST API (write operations) |
| 19 | |
| 20 | The MCP server does not currently support creating, updating, or commenting on issues. Use `gh api` for these operations. |
| 21 | |
| 22 | | Operation | Command | |
| 23 | |-----------|---------| |
| 24 | | Create issue | `gh api repos/{owner}/{repo}/issues -X POST -f title=... -f body=...` | |
| 25 | | Update issue | `gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f title=... -f state=...` | |
| 26 | | Add comment | `gh api repos/{owner}/{repo}/issues/{number}/comments -X POST -f body=...` | |
| 27 | | Close issue | `gh api repos/{owner}/{repo}/issues/{number} -X PATCH -f state=closed` | |
| 28 | | Set issue type | Include `-f type=Bug` in the create call (REST API only, not supported by `gh issue create` CLI) | |
| 29 | |
| 30 | **Note:** `gh issue create` works for basic issue creation but does **not** support the `--type` flag. Use `gh api` when you need to set issue types. |
| 31 | |
| 32 | ## Workflow |
| 33 | |
| 34 | 1. **Determine action**: Create, update, or query? |
| 35 | 2. **Gather context**: Get repo info, existing labels, milestones if needed |
| 36 | 3. **Structure content**: Use appropriate template from [references/templates.md](references/templates.md) |
| 37 | 4. **Execute**: Use MCP tools for reads, `gh api` for writes |
| 38 | 5. **Confirm**: Report the issue URL to user |
| 39 | |
| 40 | ## Creating Issues |
| 41 | |
| 42 | Use `gh api` to create issues. This supports all parameters including issue types. |
| 43 | |
| 44 | ```bash |
| 45 | gh api repos/{owner}/{repo}/issues \ |
| 46 | -X POST \ |
| 47 | -f title="Issue title" \ |
| 48 | -f body="Issue body in markdown" \ |
| 49 | -f type="Bug" \ |
| 50 | --jq '{number, html_url}' |
| 51 | ``` |
| 52 | |
| 53 | ### Optional Parameters |
| 54 | |
| 55 | Add any of these flags to the `gh api` call: |
| 56 | |
| 57 | ``` |
| 58 | -f type="Bug" # Issue type (Bug, Feature, Task, Epic, etc.) |
| 59 | -f labels[]="bug" # Labels (repeat for multiple) |
| 60 | -f assignees[]="username" # Assignees (repeat for multiple) |
| 61 | -f milestone=1 # Milestone number |
| 62 | ``` |
| 63 | |
| 64 | **Issue types** are organization-level metadata. To discover available types, use: |
| 65 | ```bash |
| 66 | gh api graphql -f query='{ organization(login: "ORG") { issueTypes(first: 10) { nodes { name } } } }' --jq '.data.organization.issueTypes.nodes[].name' |
| 67 | ``` |
| 68 | |
| 69 | **Prefer issue types over labels for categorization.** When issue types are available (e.g., Bug, Feature, Task), use the `type` parameter instead of applying equivalent labels like `bug` or `enhancement`. Issue types are the canonical way to categorize issues on GitHub. Only fall back to labels when the org has no issue types configured. |
| 70 | |
| 71 | ### Title Guidelines |
| 72 | |
| 73 | - Be specific and actionable |
| 74 | - Keep under 72 characters |
| 75 | - When issue types are set, don't add redundant prefixes like `[Bug]` |
| 76 | - Examples: |
| 77 | - `Login fails with SSO enabled` (with type=Bug) |
| 78 | - `Add dark mode support` (with type=Feature) |
| 79 | - `Add unit tests for auth module` (with type=Task) |
| 80 | |
| 81 | ### Body Structure |
| 82 | |
| 83 | Always use the templates in [references/templates.md](references/templates.md). Choose based on issue type: |
| 84 | |
| 85 | | User Request | Template | |
| 86 | |--------------|----------| |
| 87 | | Bug, error, broken, not working | Bug Report | |
| 88 | | Feature, enhancement, add, new | Feature Request | |
| 89 | | Task, chore, refactor, update | Task | |
| 90 | |
| 91 | ## Updating Issues |
| 92 | |
| 93 | Use `gh api` with PATCH: |
| 94 | |
| 95 | ```bash |
| 96 | gh api repos/{owner}/{repo}/issues/{number} \ |
| 97 | -X PATCH \ |
| 98 | -f state=closed \ |
| 99 | -f title="Updated title" \ |
| 100 | --jq '{number, html_url}' |
| 101 | ``` |
| 102 | |
| 103 | Only include fields you want to change. Available fields: `title`, `body`, `state` (open/closed), `labels`, `assignees`, `milestone`. |
| 104 | |
| 105 | ## Examples |
| 106 | |
| 107 | ### Example 1: Bug Report |
| 108 | |
| 109 | **User**: "Create a bug issue - the login page crashes when using SSO" |
| 110 | |
| 111 | **Action**: |
| 112 | ```bash |
| 113 | gh api repos/github/awesome-copilot/issues \ |
People who liked this also viewed
6 picksType
- caveman-commitUltra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. UsSkillsJul 2026
- git-guardrails-claude-codeSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- setup-pre-commitSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- resolving-merge-conflictsSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- using-git-worktreesUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackSkillsJul 2026
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanupSkillsJul 2026
