--- layout: tap site_name: github tap_name: create-issue description: "Create a GitHub issue via API" intent: write columns: - status - url args: - name: repo type: string - name: title type: string - name: body type: string - name: labels type: string args_json: | {"repo":{"type":"string"},"title":{"type":"string"},"body":{"type":"string","default":""},"labels":{"type":"string","default":""}} health_json: | {"min_rows":1,"non_empty":[]} example_args: "" source_url: https://github.com/LeonTing1010/tap-skills/blob/main/community/github/create-issue.plan.json license: MIT ---

## What it does

Create a GitHub issue via API

## Install Taprun once

Taprun ships as a single MCP server exposing a catalog of compiled taps. One-time setup on macOS / Linux:

    brew install LeonTing1010/tap/taprun
    tap mcp connect

Or drop this into your `claude_desktop_config.json` (works identically in Claude Code, Cursor, Cline, Windsurf — any MCP host):

    {
      "mcpServers": {
        "tap": {
          "command": "tap",
          "args": ["mcp", "start"]
        }
      }
    }

## Call `github/create-issue`

Terminal, once installed:

    tap run github/create-issue

From the MCP host — exact same compiled plan, deterministic replay, zero LLM tokens:

    tap.run({ site: "github", name: "create-issue" })

## Why compile it once

This plan was forged once — the AI read `github`, picked stable structural addresses (JSON-LD, ARIA, RSS, or declared API endpoints, in that priority order), and saved them to a `.plan.json`. Every replay since then has used zero LLM tokens. When `github` ships a site change that breaks the extraction, `tap verify` surfaces it before your data goes stale — not after your pipeline silently writes garbage for a week.

## Related github taps

tap | description
--- | ---
`github/trending` | GitHub repos created in the last N days with ≥ min_stars, filtered to AI/SaaS/devtool niches via topic+description keyword match. Supply-side signal for solo builder category emergence.