---
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
---

<section>
  <h2>What it does</h2>
  <p>Create a GitHub issue via API</p>
</section>

<section>
  <h2>Install Taprun once</h2>
  <p>Taprun ships as a single MCP server exposing a catalog of compiled taps. One-time setup on macOS / Linux:</p>
  <pre><code>brew install LeonTing1010/tap/taprun
tap mcp connect</code></pre>
  <p>Or drop this into your <code>claude_desktop_config.json</code> (works identically in Claude Code, Cursor, Cline, Windsurf — any MCP host):</p>
  <pre><code>{
  &quot;mcpServers&quot;: {
    &quot;tap&quot;: {
      &quot;command&quot;: &quot;tap&quot;,
      &quot;args&quot;: [&quot;mcp&quot;, &quot;start&quot;]
    }
  }
}</code></pre>
</section>

<section>
  <h2>Call <code>github/create-issue</code></h2>
  <p>Terminal, once installed:</p>
  <pre><code>tap run github/create-issue</code></pre>
  <p>From the MCP host — exact same compiled plan, deterministic replay, zero LLM tokens:</p>
  <pre><code>tap.run({ site: &quot;github&quot;, name: &quot;create-issue&quot; })</code></pre>
</section>

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

<section>
  <h2>Related github taps</h2>
  <table><thead><tr><th>tap</th><th>description</th></tr></thead><tbody>
    <tr><td><a href="/taps/github/trending"><code>github/trending</code></a></td><td>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.</td></tr>
  </tbody></table>
</section>