github/awesome-copilot

github-issues

Create, update, and manage GitHub issues using MCP tools.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/github/awesome-copilot --skill github-issues

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

GitHub Issues

Manage GitHub issues using the @modelcontextprotocol/server-github MCP server.

Available Tools

MCP Tools (read operations)

ToolPurpose
mcp__github__issue_readRead issue details, sub-issues, comments, labels (methods: get, getcomments, getsubissues, getlabels)
mcp__github__list_issuesList and filter repository issues by state, labels, date
mcp__github__search_issuesSearch issues across repos using GitHub search syntax
mcp__github__projects_listList projects, project fields, project items, status updates
mcp__github__projects_getGet details of a project, field, item, or status update
mcp__github__projects_writeAdd/update/delete project items, create status updates

MCP Tools (write operations)

ToolPurpose
mcp__github__issue_writeCreate or update an issue (methods: create, update). Supports title, body, type, labels, assignees, milestone, and issue fields
mcp__github__add_issue_commentAdd a comment or a reaction to an issue
mcp__github__sub_issue_writeAdd, remove, or reprioritize a sub-issue

CLI / REST API (write operations)

gh api performs the same writes and is the form used in the examples below. Reach for it when the MCP server is not connected, or when you need a REST field the MCP tools do not expose.

OperationCommand
Create issuegh api repos/{owner}/{repo}/issues -X POST -f title=... -f body=...
Update issuegh api repos/{owner}/{repo}/issues/{number} -X PATCH -f title=... -f state=...
Add commentgh api repos/{owner}/{repo}/issues/{number}/comments -X POST -f body=...
Close issuegh api repos/{owner}/{repo}/issues/{number} -X PATCH -f state=closed
Set issue typeInclude -f type=Bug in the create call (REST API only, not supported by gh issue create CLI)

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.

Workflow

  1. Determine action: Create, update, or query?
  2. Gather context: Get repo info, existing labels, milestones if needed
  3. Structure content: Use appropriate template from references/templates.md
  4. Execute: Use MCP tools for reads, gh api for writes
  5. Confirm: Report the issue URL to user

Creating Issues

Use gh api to create issues. This supports all parameters including issue types.

bash
gh api repos/{owner}/{repo}/issues \
  -X POST \
  -f title="Issue title" \
  -f body="Issue body in markdown" \
  -f type="Bug" \
  --jq '{number, html_url}'

Optional Parameters

Add any of these flags to the gh api call:

-f type="Bug"                    # Issue type (Bug, Feature, Task, Epic, etc.)
-f 'labels[]=bug'                # Labels (repeat for multiple)
-f 'assignees[]=username'        # Assignees (repeat for multiple)
-f milestone=1                   # Milestone number

Quote the whole `name[]=value` pair. [] is a glob pattern in zsh, the default shell on macOS, so an unquoted -f labels[]=bug never reaches gh:

zsh: no matches found: labels[]=bug

Issue types are organization-level metadata. To discover available types, use:

bash
gh api graphql -f query='{ organization(login: "ORG") { issueTypes(first: 10) { nodes { name } } } }' --jq '.data.organization.issueTypes.nodes[].name'

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.

Title Guidelines

  • Be specific and actionable
  • Keep under 72 characters
  • When issue types are set, don't add redundant prefixes like [Bug]
  • Examples:
  • Login fails with SSO enabled (with type=Bug)
  • Add dark mode support (with type=Feature)
  • Add unit tests for auth module (with type=Task)

Body Structure

Always use the templates in references/templates.md. Choose based on issue type:

User RequestTemplate
Bug, error, broken, not workingBug Report
Feature, enhancement, add, newFeature Request
Task, chore, refactor, updateTask

Updating Issues

Use gh api with PATCH:

bash
gh api repos/{owner}/{repo}/issues/{number} \
  -X PATCH \
  -f state=closed \
  -f title="Updated title" \
  --jq '{number, html_url}'

Only include fields you want to change. Available fields: title, body, state (open/closed), labels, assignees, milestone.

Examples

Example 1: Bug Report

User: "Create a bug issue - the login page crashes when using SSO"

Action:

bash
gh api repos/github/awesome-copilot/issues \
  -X POST \
  -f title="Login page crashes when using SSO" \
  -f type="Bug" \
  -f body="## Description
The login page crashes when users attempt to authenticate using SSO.

## Steps to Reproduce
1. Navigate to login page
2. Click 'Sign in with SSO'
3. Page crashes

## Expected Behavior
SSO authentication should complete and redirect to dashboard.

## Actual Behavior
Page becomes unresponsive and displays error." \
  --jq '{number, html_url}'

Example 2: Feature Request

User: "Create a feature request for dark mode with high priority"

Action:

bash
gh api repos/github/awesome-copilot/issues \
  -X POST \
  -f title="Add dark mode support" \
  -f type="Feature" \
  -f 'labels[]=high-priority' \
  -f body="## Summary
Add dark mode theme option for improved user experience and accessibility.

## Motivation
- Reduces eye strain in low-light environments
- Increasingly expected by users

## Proposed Solution
Implement theme toggle with system preference detection.

## Acceptance Criteria
- [ ] Toggle switch in settings
- [ ] Persists user preference
- [ ] Respects system preference by default" \
  --jq '{number, html_url}'

Common Labels

Use these standard labels when applicable:

LabelUse For
bugSomething isn't working
enhancementNew feature or improvement
documentationDocumentation updates
good first issueGood for newcomers
help wantedExtra attention needed
questionFurther information requested
wontfixWill not be addressed
duplicateAlready exists
high-priorityUrgent issues

Tips

  • Always confirm the repository context before creating issues
  • Ask for missing critical information rather than guessing
  • Link related issues when known: Related to #123
  • For updates, fetch current issue first to preserve unchanged fields

Extended Capabilities

The following features require REST or GraphQL APIs beyond the basic MCP tools. Each is documented in its own reference file so the agent only loads the knowledge it needs.

CapabilityWhen to useReference
Advanced searchComplex queries with boolean logic, date ranges, cross-repo search, issue field filters (field.name:value)references/search.md
Sub-issues & parent issuesBreaking work into hierarchical tasksreferences/sub-issues.md
MilestonesCreate, read, update, close, reopen, delete milestones and manage milestone issuesreferences/milestones.md
LabelsDiscover, create, rename, recolor, and delete repository labels; add or replace labels on an issuereferences/labels.md
Issue dependenciesTracking blocked-by / blocking relationshipsreferences/dependencies.md
Issue types (advanced)GraphQL operations beyond MCP list_issue_types / type paramreferences/issue-types.md
Projects V2Project boards, progress reports, field managementreferences/projects.md
Issue fieldsCustom metadata: dates, priority, text, numbers (private preview)references/issue-fields.md
Images in issuesEmbedding images in issue bodies and comments via CLIreferences/images.md

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills
github
Ufficiale

anti-ui-slop

Stop coding agents from shipping generic UI. Use UIZZE''s 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".

Installazioni / 1h
7
GitHub Stars
41,4K
Aggiornato
20 nov
github
Ufficiale

javascript-typescript-jest

Best practices for writing JavaScript/TypeScript tests using Jest, including mocking strategies, test structure, and common patterns.

Installazioni / 1h
4
GitHub Stars
41,4K
Aggiornato
20 nov
github
Ufficiale

multi-stage-dockerfile

Create optimized multi-stage Dockerfiles for any language or framework

Installazioni / 24h
446
GitHub Stars
41,4K
Aggiornato
20 nov
github
Ufficiale

sql-code-review

Universal SQL code review assistant that performs comprehensive security, maintainability, and code quality analysis across all SQL databases (MySQL, PostgreSQL, SQL Server, Oracle). Focuses on SQL injection prevention, access control, code standards, and anti-pattern detection. Complements SQL optimization prompt for complete development coverage.

Installazioni / 24h
437
GitHub Stars
41,4K
Aggiornato
20 nov