superspecs: Skill for Claude Code

Skill: github-issues

You read GitHub issues for the current project so a human (or /superspecs:discuss) has real context before planning. This skill is read-only: it never creates, edits, comments on, or closes anything on GitHub.

Prerequisite: a github MCP server must be configured in this project's .mcp.json (created by setup.sh — see "MCP Setup" below) and the tools it exposes must be available. If no github-prefixed MCP tool is available, stop and say:

"No GitHub MCP server is connected. Check .mcp.json for a github entry, and make sure GITHUB_PERSONAL_ACCESS_TOKEN (and GITHUB_HOST, if this is GitHub Enterprise Server) are exported in your shell before starting this session."

MCP Setup (per project, configurable)

setup.sh writes a default .mcp.json pointing at the official github-mcp-server (via Docker) configured for github.com:

{
  "mcpServers": {
    "github": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "GITHUB_PERSONAL_ACCESS_TOKEN", "ghcr.io/github/github-mcp-server"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
      }
    }
  }
}

This is only written if .mcp.json doesn't already exist — an existing file is never overwritten. Each project configures its own credentials by exporting GITHUB_PERSONAL_ACCESS_TOKEN in its own shell/CI environment. Nothing secret is ever committed.

For a self-hosted GitHub Enterprise Server instance: add a GITHUB_HOST entry to both args and env in .mcp.json:

"args": ["run", "-i", "--rm", "-e", "GITHUB_PERSONAL_ACCESS_TOKEN", "-e", "GITHUB_HOST", "ghcr.io/github/github-mcp-server"],
"env": {
  "GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}",
  "GITHUB_HOST": "${GITHUB_HOST}"
}

...then export GITHUB_HOST=https://github.<your-company>.com alongside the token. This is a one-time, per-project edit — setup.sh never assumes GHE for you, since the same framework installs into both github.com and GHE projects.