github-create

A command that creates a GitHub issue for a SpecWeave increment from its local specification documents. The issue includes user stories, acceptance criteria, task checklists, labels, and a milestone.

In plain words
What is it for?
Use it to sync an increment’s living documents and create its linked GitHub issue, with options to force creation or set labels.
Why use it?
It turns the project’s structured planning documents into a GitHub issue without making you copy the details manually.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/anton-abyzov/specweave/github-create
Clone the repo
git clone --depth 1 https://github.com/anton-abyzov/specweave
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,904 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00032 $0.01904
Opus 5 $0.00016 $0.00952
Sonnet 5 $0.00006 $0.00381
Haiku 4.5 $0.00003 $0.00190

Measured 2d ago against content hash 52c072295e9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-create scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/specweave/commands/github-create.md · 331 lines

How it starts

The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create GitHub Issue from Increment

Create a GitHub issue for the specified SpecWeave increment.

⛔ MANDATORY: Sync Living Docs BEFORE Creating Issue

GitHub issue content is generated FROM living docs. If living docs don't exist or are stale, the issue will be incomplete.

You MUST run sw:sync-specs BEFORE creating (unless using sw:sync-progress):

# STEP 1: Ensure living docs exist and are current
sw:sync-specs <increment-id>

# STEP 2: Then create GitHub issue
sw-github:create <increment-id>

Why?

  • Issue body is generated from .specweave/docs/internal/specs/FS-XXX/
  • User stories and ACs come from living docs
  • Task checklist reflects living docs structure
  • Without sync-specs, issue will be created from raw increment spec.md (less structured)

Note: sw:sync-progress calls sync-specs automatically before creating issues.


Usage: sw-github:create <increment-id>

sw:github:create-issue <increment-id> [options]

Arguments

  • increment-id: Increment ID (e.g., 0004 or 0004-plugin-architecture)

Options

  • --force: Force create even if issue already exists
  • --labels: Comma-separated labels (default: from config)
  • --milestone: Milestone name (default: from config)
  • --assignee: Assign to user (@username)
  • --project: Add to GitHub project (project number)

Examples

# Basic usage
sw:github:create-issue 0004

# With custom labels
sw:github:create-issue 0004 --labels "urgent,backend"

# Assign to developer
sw:github:create-issue 0004 --assignee @developer1

# Add to project
sw:github:create-issue 0004 --project 3

# Force recreate
sw:github:create-issue 0004 --force

What This Command Does

  1. Loads Increment

    • Reads .specweave/increments/<increment-id>/
    • Parses spec.md, plan.md, tasks.md
    • Checks .metadata.yaml for existing issue
  2. Detects Repository

    • Extracts repo from git remote
    • Format: owner/repo
    • Verifies write permissions

Read the full file on GitHub · 331 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 331 lines · 32 tokens per session scan A 52c072295e9a

Subscribe to this mod's changes

github-create is a command published in the GitHub repository anton-abyzov/specweave (159 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 1,904 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.