← ClaudeAtlas

github-issueslisted

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, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task.
eric-sabe/engsys · ★ 1 · AI & Automation · score 67
Install: claude install-skill eric-sabe/engsys
# GitHub Issues Manage GitHub issues using `gh` CLI (preferred) with `user-github` MCP server as fallback. **Important:** The GitHub MCP does **not** support GitHub Projects (ProjectV2). For project board operations (priorities, status, custom fields, waves), always use `gh project` or `gh api graphql`. ## Tool Priority 1. **`gh` CLI** (preferred) — full coverage, projects support, GraphQL access 2. **GitHub MCP** (fallback) — use when `gh` CLI has auth or connectivity issues ## Available MCP Tools (fallback only) | Tool | Purpose | | -------------------------------- | ---------------------- | | `mcp__github__create_issue` | Create new issues | | `mcp__github__update_issue` | Update existing issues | | `mcp__github__get_issue` | Fetch issue details | | `mcp__github__search_issues` | Search issues | | `mcp__github__add_issue_comment` | Add comments | | `mcp__github__list_issues` | List repository issues | ## 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](references/templates.md) 4. **Execute**: Use `gh` CLI first; fall back to MCP tools if CLI has issues 5. **Confirm**: Report the issue URL to user ## Creating Issues ### Using gh CLI (preferred) ```bash # Write body to tmp/ file first, then: gh issue c