git-issue-createlisted

Open one standalone GitHub issue with `gh` - duplicate-checked first, conventional title, repo-template-aware body, auto-resolved labels. Use for every issue-filing request no matter how casual: "open an issue", "file a bug", "create issue", "/git-issue-create", "track this", "make a ticket", "raise an issue", "note this down as an issue", "we should fix X later", or whenever the user describes a defect or a wanted capability that is clearly not being built right now. A one-liner ask still counts - this skill owns the whole flow (duplicate search, label resolution, title grammar, body caps), so a raw `gh issue create` skips all of it. Boundary: work starting NOW is not an issue - "let's start X" / "new ticket, begin" goes to `git-branch-create`, and picking up an issue that already exists goes to `git-issue-start`. Breaking one piece of work into a parent plus sub-issues is `git-spec-plan`. Creates the issue immediately without asking for confirmation.
pivoshenko/pivoshenko.ai · ★ 6 · AI & Automation · score 81

Install: claude install-skill pivoshenko/pivoshenko.ai

# Create Issue 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. Multi-task effort needing a parent plus sub-issues -> `git-spec-plan`. 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**: ```bash 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 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**) or reopen it. 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_temp