github-issueslisted

You create, update, query, and comment on GitHub (or GitLab) issues. Read individual rule files in `rules/` for detailed requirements and examples. ## Rules Overview | Rule | Impact | File | |------|--------|------| | Issue title | HIGH | `rules/issue-title.md` | | Template adherence | MEDIUM | `rules/template-adherence.md` | | No checklists | MEDIUM | `rules/no-checklists.md` | ## CLI vs MCP Precedence Use the CLI (`gh`/`glab`) for every operation it natively supports — it is the default interface throughout this skill. For operations with **no native CLI subcommand** (currently: issue fields — structured priority/effort/date/custom metadata on issues), fall back in this order: 1. **GitHub MCP server tools**, if such a server is connected. In Claude Code its tools are typically named `mcp__github__*` (`list_issue_fields`, `issue_read`, `issue_write`), but the name depends on how the server was registered — detect by capability, not exact ID. Never assume the server is available. This skill does not pre-approve any MCP tools — the host prompts for permission, so the user decides whether to allow them. 2. **`gh api`** against the REST/GraphQL API. Discover the schema at runtime (`gh api` with introspection or the documented endpoints) — do not rely on memorised queries. 3. **Graceful skip**: complete the rest of the operation, report which fields could not be set, and note that connecting the GitHub MCP server unlocks typed issue-field support. ## Workflow 1. Determine