github-issues
Create, 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 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", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management
Profile →npx skills add github/awesome-copilot --skill github-issues --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# GitHub Issues Manage GitHub issues using the `@modelcontextprotocol/server-github` MCP server. ## Available Tools ### MCP Tools (read operations) | Tool | Purpose | |------|---------| | `mcp__github__issue_read` | Read issue details, sub-issues, comments, labels (methods: get, get_comments, get_sub_issues, get_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__github__projects_list` | List projects, project fields, project items, status updates | | `mcp__github__projects_get` | Get details of a project, field, item, or status update | | `mcp__github__projects_write` | Add/update/delete project items, create status updates | ### CLI / REST API (write operations) The MCP server does not currently support creating, updating, or commenting on issues. Use `gh api` for these operations. | 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=... -f state=...` | | Add comment | `gh api
- Available Tools
- MCP Tools (read operations)
- CLI / REST API (write operations)
- Workflow
- Creating Issues
- Optional Parameters
- Title Guidelines
- Body Structure
- Updating Issues
- Examples
- Example 1: Bug Report
- Example 2: Feature Request
- Common Labels
- Tips
gh api repos/{owner}/{repo}/issues \
gh api graphql -f query='{ organization(login: "ORG") { issueTypes(first: 10) { nodes { name } } } }' --jq '.data.organization.issueTypes.nodes[].name'
gh api repos/{owner}/{repo}/issues/{number} \
gh api repos/github/awesome-copilot/issues \
The login page crashes when users attempt to authenticate using SSO.
SSO authentication should complete and redirect to dashboard.
Page becomes unresponsive and displays error." \
Add dark mode theme option for improved user experience and accessibility.
Implement theme toggle with system preference detection.What does the github-issues skill do?
Create, 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 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", "link issues", "add dependency", "blocked by", "blocking", or any GitHub issue management
How do I install it?
Run `npx skills add github/awesome-copilot --skill github-issues --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.