git-issue-create

Git Issue Create

File one standalone issue. No confirm.

Flow

1. Boundary check: is the work starting now? Yes -> hand off to git-branch-create (new work) or git-issue-start (issue already exists) and stop. Why -> an issue is a record of work deferred; work in flight belongs on a branch, and a second tracker entry for it just rots
2. Repo: gh repo view --json nameWithOwner -q .nameWithOwner. Fails -> stop, surface the error (no remote, no auth, not a repo). Never guess owner/name
3. Search for duplicates before drafting anything:

   gh issue list --search "<2-4 distinctive keywords>" --state all --limit 10 \
     --json number,title,state,url -q '.[] | "\(.number)\t\(.state)\t\(.title)"'
   

   --state all -> a closed issue is the answer often enough that skipping it files the same bug twice. Keywords are nouns from the user's description, not the whole sentence. 10 hits returned -> the search was too broad and real duplicates may sit past the cap; narrow the keywords and search again before proceeding
4. Triage the hits:
   • Strong match (same defect, same capability) -> print its number, title, state, URL. Stop. Offer to comment on it instead (<= 4 prose lines, see Length); reopening is the user's call, not this skill's. Why -> a duplicate backlog is worse than a missing issue: every triage pass afterwards pays for it
   • Adjacent match (related, not the same) -> proceed, link it in ## Context
   • No hits -> proceed
5. Parallel:
   • Repo issue template: .github/ISSUE_TEMPLATE/*.md, .github/ISSUE_TEMPLATE/*.yml, .github/issue_template.md, root issue_template.md (first match wins)
   • gh label list --limit 200 --json name -q '.[].name'
6. Draft title per Title. Draft body:
   • Template found -> fill that template's structure (preserve headings, order, checklists, HTML comments). A *.yml form -> render its label/attributes as markdown headings in the same order
   • None found (the normal case) -> use Fallback Body below
7. Resolve labels per Labels. Exactly one type: *
8. Heredoc body so markdown survives the shell:

   gh issue create --title "fix(auth): session drops on api deploy" --label "type: bug" --body "$(cat <<'EOF'
   ## Problem
   
   Sessions drop on every API deploy because the cookie is signed with a per-instance key.
   
   ## Done when
   
   - a session survives a rolling restart of all API pods
   - no change required to the `users` table
   EOF
   )"
   

   'EOF' quoted -> no shell interpolation, so $, backticks and # in the body survive intact
9. Print the issue URL. Name any label dropped in step 7 and why
10. User wants to start on it now -> hand off to git-issue-start