github-issue-create
GitHub Issue Create
Turn user, repo, or source-issue context into actionable GitHub issue drafts, then create approved issues and approved native GitHub relationships with gh.
AFK = implementable end-to-end without human input. HITL = blocked on a real human decision such as design, product, or architecture.
For multi-step work, start with a short user-visible update that says what repository or source context you are checking first.
Goal
Produce issue drafts a maintainer can act on, get explicit approval, then publish exactly the approved issue set.
Success Criteria
- Drafts use facts from the user, repo, or fetched source issue.
- Each issue has a clear title, observable acceptance criteria, useful metadata, and proportional scope.
- Multi-issue implementation plans are tracer-bullet vertical slices unless an architecture exception is justified.
- Likely duplicates are surfaced before creation.
- No issue, label, or native relationship is created before explicit approval.
More from marcellocurto/skills
wild-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.
7simplify-code-solution
Simplify code fixes and feature proposals by grounding them in real requirements and existing code. Use when a coding plan feels overbuilt, speculative, too abstract, or needs assumptions challenged before implementation.
6