github-issue-quick-create
GitHub Issue Quick Create
Draft one straightforward GitHub issue, then create it with gh after explicit approval.
Use this for one simple bug, task, chore, or feature. Use github-issue-create for complex issue work.
Goal
Give the user one usable issue draft with minimal metadata, then create it only after explicit approval.
Success Criteria
- The user sees one clear draft with repo, title, body, and any explicit labels or assignees.
- The draft uses only details from the user, repository, or narrowly inspected code.
- Missing details are requested only when the draft would be unusable.
- No issue is created until the user explicitly approves the draft.
- The final response includes the issue number, title, and URL.
Constraints
More from marcellocurto/skills
github-issue-create
Draft and create GitHub issues with `gh`. Use for bugs, tasks, features, PRDs, specs, epics, sub-issues, blockers, and tracer-bullet vertical issue breakdowns. Draft first. After approval, create issues and approved native GitHub relationships in the same turn.
11wild-frontend
Explicit-only skill for unconstrained, highly creative frontend design. Use only when the user explicitly says to use wild-frontend or asks to invoke this exact skill. Do not trigger automatically for normal frontend, styling, beautification, product UI, design-system, or production polish requests.
8bug-fix-planner
Plan a concrete fix for a specific bug, regression, crash, failing test, error, or broken behavior without changing code. Use when the user wants a path forward from a bug report, GitHub issue, stack trace, logs, screenshots, repro steps, or failing test. Do not use for new features, broad refactors, general debugging advice, or requests to directly implement the fix.
7design-system-ui
Design and implement polished frontend UI that feels native to the existing product, codebase, component library, and design system. Use for normal production frontend work where the result should extend real project patterns rather than invent a disconnected visual direction.
7relentless-review
Relentlessly stress-test proposals, plans, implementations, designs, strategies, or answers. Use when the user asks "is this actually the best we can do?", wants assumptions challenged, edge cases explored, failure modes examined, or asks to push harder, red-team, find holes, or be relentless. The answer may be that the current work is already the best path and should not change. Do not use for proofreading, encouragement-only feedback, minor style review, or requests where the user only wants implementation.
7test-quality-audit
Audit tests for real bug-finding value. Use when the user asks whether tests are useful, trivial, redundant, over-mocked, implementation-coupled, snapshot-heavy, coverage-padding, only passing because the test controls both sides, or whether tests should be kept, fixed, cut, or added. Also use when reviewing test changes in a PR and the user wants honest judgment about whether the tests earn their place.
7