what-iff: Skill for Claude Code

File a GitHub issue (public repo only)

Everything here is world-readable forever. No internal hostnames, customer names, private-repo paths, Jira keys, Notion links, or session URLs in the title or body.

1. Guard

REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
[ "$REPO" = theimaginaryfoundation/what-iff ] || { echo "not the public repo ($REPO); stop"; exit 1; }

Stop if gh is missing or unauthenticated (gh auth status); do not fall back to the raw API, a browser, or another tracker.

2. Dedupe

gh issue list -S "<2-4 keywords> in:title" --state all -L 5 --json number,title,state

If one matches, comment there or report it to the user instead of filing.

3. File

Body headings must match the form labels exactly (GitHub renders form submissions as ### <label> sections; same headings → same look and same searchability). Drop optional sections you have nothing for.

Bug (-l bug):

gh issue create -l bug -t "<symptom, ≤72 chars, no prefix>" -F - <<'BODY'
### Area

<one of: API / backend (Go) | Web app (web/app) | Data layer (ent, migrations, Postgres) | LLM providers / agent | CI / Docker / build | Docs | Other>

### What happened

<observed behavior + exact error/log lines, trimmed>

### What you expected

<...>

### Steps to reproduce

1. ...

### Version or commit

<git rev-parse --short HEAD, or tag>

### Environment

<OS, Go/Node, docker compose vs make run, provider, browser — only what matters>

### Additional context

<related issues/PRs as #N, suspected cause, workaround>
BODY

Feature (-l enhancement):

gh issue create -l enhancement -t "<outcome, ≤72 chars>" -F - <<'BODY'
### Area

<same list as above>

### Problem

<what is hard today, and for whom>

### Proposed solution

<what changes; API/UI/config shape if known>

### Alternatives considered

<...>

### Additional context

<links, prior art, willing to implement?>
BODY

Report the URL gh prints. Only add -a @me, -m, or extra labels if asked.