create-issue

name	create-issue
description	Create a GitHub issue and add it to the Typhon dev project

Create GitHub Issue for Typhon

Create a GitHub issue and add it to the "Typhon dev" project (project #7).

Input provided by user

$ARGUMENTS

Help

If $ARGUMENTS contains --help or -h, display the following and stop — do not execute the workflow.

/create-issue [title]

  Create a GitHub issue and add it to the Typhon dev project.

Arguments:
  title           Issue title text — if provided, skips the title prompt
  --help, -h      Show this help

What it does:
  1. Gathers required info (title, description, labels, area, priority, phase, estimate)
  2. Creates the issue via GitHub API
  3. Adds it to the Typhon dev project board
  4. Sets project fields (priority, phase, area, estimate)

Examples:
  /create-issue
  /create-issue "Add spatial indexing support"

Required information

You need to gather the following information. If NOT provided in the arguments above, use the AskUserQuestion tool to ask the user:

1. Title (required): A clear, concise issue title
2. Description (required): What needs to be done and why
3. Type labels (optional): One or more of: bug, enhancement, documentation, performance, refactoring, testing, technical-debt, question
4. Area (optional - project field): Database, MVCC, Transactions, Indexes, Schema, Storage, Memory, Concurrency, Primitives
5. Priority (optional): P0-Critical, P1-High, P2-Medium, P3-Low
6. Phase (optional): Telemetry, Query, WAL, Reliability, Infrastructure
7. Estimate (optional): T-shirt size: XS, S, M, L, XL

Gathering information

• If the user provided a clear title and description in their arguments, proceed directly
• If information is missing or unclear, use AskUserQuestion to ask for it
• For labels, area, priority, phase, and estimate, offer them as options in AskUserQuestion with multi-select for labels
• Be conversational and helpful when asking questions

Example questions to ask:

If title is missing:

Question: "What should the issue title be?"
Options: Let user type freely (no predefined options needed - just ask in text)

If description is missing:

Question: "Can you describe what needs to be done?"

For type labels (if not provided):

Question: "What type of issue is this?"
Header: "Type"
Options: bug, enhancement, documentation, performance, refactoring, testing, technical-debt
MultiSelect: true

For area (if not provided):

Question: "Which area of the codebase does this primarily affect?"
Header: "Area"
Options:
  - Database (DatabaseEngine, ComponentTable, API)
  - Transactions (Transaction, TransactionChain)
  - MVCC (Revisions, snapshot isolation)
  - Indexes (B+Tree implementations)
  - Schema (Component definitions, attributes)
  - Storage (PagedMMF, segments, persistence)
  - Memory (Allocators, memory blocks)
  - Concurrency (Locks, AccessControl)
  - Primitives (String64, Variant, collections)
MultiSelect: false

For priority (if not provided):

Question: "What priority level?"
Header: "Priority"
Options:
  - P0-Critical (blocking, needs immediate attention)
  - P1-High (important, should be done soon)
  - P2-Medium (normal priority)
  - P3-Low (nice to have, do when time permits)

For phase (if relevant):

Question: "Is this part of a specific development phase?"
Header: "Phase"
Options:
  - Telemetry (observability, metrics, diagnostics)
  - Query (query engine, filtering, sorting)
  - WAL (write-ahead logging, recovery)
  - Reliability (error handling, resilience)
  - Infrastructure (tooling, CI/CD, docs)
  - None (standalone issue)

For estimate (if not provided):

Question: "How would you estimate the effort?"
Header: "Estimate"
Options:
  - XS (trivial, < 1 hour)
  - S (small, half a day)
  - M (medium, 1-2 days)
  - L (large, 3-5 days)
  - XL (extra large, 1+ week)

Creating the issue

Once you have the required information:

IMPORTANT: When writing the issue body, always use absolute URLs for any links to files in the repo. Relative paths like [text](claude/foo.md) break when viewed outside the repo context (e.g., on the project board). Use https://github.com/nockawa/Typhon/blob/main/<path> for files and https://github.com/nockawa/Typhon/tree/main/<path> for directories. See .claude/skills/_helpers.md rule #9.

Step 1: Create the issue

Use mcp__GitHub__create_issue with:

• owner: "nockawa"
• repo: "Typhon"
• title: "<title>"
• body: "<description>"
• labels: ["<label1>", "<label2>"]
• assignees: ["nockawa"]

Note: Issues are always assigned to nockawa by default.

Step 2: Get the issue number and URL from the returned object

Step 3: Add to project

gh project item-add 7 --owner nockawa --url <issue_url>

Step 4: Get the project item ID

Project item lookup: Read .claude/skills/_helpers.md Section 2 for the robust patterns.

# Find the item ID by piping directly to Python (no temp files)
gh project item-list 7 --owner nockawa --limit 200 --format json 2>&1 | python3 -c "
import json, sys
items = json.load(sys.stdin)['items']
for item in items:
    if item.get('content', {}).get('number') == int(sys.argv[1]):
        print(item['id'])
        sys.exit(0)
print('NOT_FOUND')
" <issue_number>

Step 5: Set project fields

Use the field IDs below to set the appropriate fields:

# Set multiple fields for the item
gh project item-edit --project-id PVT_kwHOAud1ac4BNdCj --id ITEM_ID \
  --field-id FIELD_ID --single-select-option-id OPTION_ID

Umbrella issues (parent-of-many)

If the issue represents a multi-phase effort and the user wants separate tracking issues for each phase, treat it as an umbrella and do two things:

1. Include a [tasklist] block in the body with one #N reference per sub-issue — this is what humans read in the rendered markdown.
2. Link each sub-issue natively via the GitHub Sub-issues API — this is what drives the Sub-issues section in the GitHub UI (separate from the text body). GitHub's sub_issues_summary on the umbrella reflects only the native links, not the [tasklist] text.

How to link natively — for each sub-issue, get its database id (the big integer in the issue's JSON, not the small issue number) and POST it to the umbrella's sub_issues endpoint. Use gh api -F (not -f) so the id is serialized as a JSON integer, not a string:

# Get each sub-issue's database id
SUB_ID=$(gh api repos/nockawa/Typhon/issues/<sub_number> --jq '.id')

# Link it as a native sub-issue of the umbrella
gh api repos/nockawa/Typhon/issues/<umbrella_number>/sub_issues -X POST -F sub_issue_id=$SUB_ID

Verify:

gh api repos/nockawa/Typhon/issues/<umbrella_number>/sub_issues | python3 -c "
import json, sys
for s in json.load(sys.stdin):
    print(f'#{s[\"number\"]} - {s[\"title\"]} [{s[\"state\"]}]')
"

Recap: the [tasklist] block gives you a checkbox-driven progress view embedded in the body (good for narrative + markdown tooling like /complete-subtask that checks the box). The native sub-issues linkage gives you GitHub's first-class UI — the "Sub-issues" panel, roll-up progress bar, and breadcrumb on the child. Do both when creating an umbrella — they serve different surfaces.

If the user asks to retroactively convert an existing umbrella (body has [tasklist] but sub_issues_summary.total is 0), run the linking loop above — no need to edit the body.

Field Reference

Project ID

• PVT_kwHOAud1ac4BNdCj

Status Field

• Field ID: PVTSSF_lAHOAud1ac4BNdCjzg8cXYI
• Options:
  • Backlog: 11d8e01f
  • Research: 6aea77c6
  • Ready: 303600de
  • In Progress: a0a7aab6
  • Review: fadead67
  • Done: 12503e99

Priority Field

• Field ID: PVTSSF_lAHOAud1ac4BNdCjzg8c8uQ
• Options: Look up via gh project field-list 7 --owner nockawa --format json

Phase Field

• Field ID: PVTSSF_lAHOAud1ac4BNdCjzg8c8uU
• Options: Look up via gh project field-list 7 --owner nockawa --format json

Area Field

• Field ID: PVTSSF_lAHOAud1ac4BNdCjzg8cX_E
• Options: Look up via gh project field-list 7 --owner nockawa --format json

Estimate Field

• Field ID: PVTSSF_lAHOAud1ac4BNdCjzg8cYEU
• Options: Look up via gh project field-list 7 --owner nockawa --format json

Target Date Field

• Field ID: PVTF_lAHOAud1ac4BNdCjzg8c8uc
• Set with: --date "2026-02-15"

Output

After creating the issue, report back to the user with:

• Issue number and title
• Link to the issue
• Confirmation it was added to "Typhon dev" project
• The fields that were set (Priority, Phase, Area, Estimate)

Example interaction

User: /create-issue Add support for spatial indexing

Claude: Asks for description, area, priority, and estimate

User: Provides answers

Claude: Creates issue, adds to project, sets fields, reports success

Issue #15 created: "Add support for spatial indexing"
   Link: https://github.com/nockawa/Typhon/issues/15
   Added to "Typhon dev" project
   Assigned to: nockawa
   Priority: P2-Medium
   Phase: Query
   Area: Indexes
   Estimate: L (large)
   Labels: enhancement, performance