Create issue
Turn the user's input into an implementation-ready issue grounded in the current
repository, then create it after the required review boundary.
Gates
- Investigate before drafting: read the applicable project instructions and
vision, search open and closed issues for duplicates of the outcome as well
as the mechanism, and inspect the affected code, tests, and docs.
- When
grill-with-docs or grill-me is registered, run its actual
user-question loop before drafting. Prefer grill-with-docs. If neither is
available, note that once and continue.
- Stop before drafting when the request conflicts with project vision, is a
duplicate, or needs material facts that cannot be established. For a
duplicate, return the existing issue and stop without asking whether to file
the same request anyway or mutate the existing issue.
- Before posting, resolve the authenticated GitHub username and exact model name
from the current GitHub account and agent environment. Stop if either is
unavailable; never guess or substitute a generic label.
Automatic mode
Automatic mode applies only when the original prompt says automatic or
explicitly requests it. Complete every gate, then choose the template, title,
labels, and body from project evidence and create the issue without draft
approval. Material ambiguity or risk disables automatic mode.
Workflow
Discover the repository's issue templates and existing label conventions.
Investigate the request using the gates above. Ground any progress claim in
evidence gathered this run.
Run the registered grill skill and incorporate the result.
Draft against the matching template. Keep only decision-, implementation-,
and verification-relevant content:
- a specific plain-language title;
- problem, current and expected behavior, scope, constraints, and required
behavior;
- reproduction and regression expectations for bugs;
- user/test impact, likely affected area, and related work where relevant.
For UI/UX work, add the affected states, current and expected visual evidence,
accessibility expectations, responsive/theme scope, and applicable design
system components or tokens. Upload local screenshots and videos with
gh issue create --attach '<file>#<alt text>' (or gh issue edit and
gh issue comment with the same flag); never commit evidence media to the
repository. Put non-media evidence such as probe output inside a collapsed
<details> block.
Choose only existing labels unless the user asks to create one.
Show the proposed title, labels, and body unless the user waived review or
automatic mode applies.
End the issue body with this visually separate GitHub Note, replacing both
values with the exact identities resolved for this run:
[!NOTE]
Created on behalf of @username using ModelName.
Create the issue with the available GitHub tooling and return its URL.
Lead with the outcome. Omit boilerplate, repeated summaries, and a narration of
the workflow.
1---2name: create-issue3description: Investigates and creates a project-aligned GitHub issue from a tagline or short description, using the repository's template, evidence, and labels. Use when the user runs /create-issue or asks to file a GitHub issue.4license: Unlicense OR MIT5---67# Create issue89Turn the user's input into an implementation-ready issue grounded in the current10repository, then create it after the required review boundary.1112## Gates1314- Investigate before drafting: read the applicable project instructions and15 vision, search open and closed issues for duplicates of the outcome as well16 as the mechanism, and inspect the affected code, tests, and docs.17- When `grill-with-docs` or `grill-me` is registered, run its actual18 user-question loop before drafting. Prefer `grill-with-docs`. If neither is19 available, note that once and continue.20- Stop before drafting when the request conflicts with project vision, is a21 duplicate, or needs material facts that cannot be established. For a22 duplicate, return the existing issue and stop without asking whether to file23 the same request anyway or mutate the existing issue.24- Before posting, resolve the authenticated GitHub username and exact model name25 from the current GitHub account and agent environment. Stop if either is26 unavailable; never guess or substitute a generic label.2728## Automatic mode2930Automatic mode applies only when the original prompt says `automatic` or31explicitly requests it. Complete every gate, then choose the template, title,32labels, and body from project evidence and create the issue without draft33approval. Material ambiguity or risk disables automatic mode.3435## Workflow36371. Discover the repository's issue templates and existing label conventions.382. Investigate the request using the gates above. Ground any progress claim in39 evidence gathered this run.403. Run the registered grill skill and incorporate the result.414. Draft against the matching template. Keep only decision-, implementation-,42 and verification-relevant content:43 - a specific plain-language title;44 - problem, current and expected behavior, scope, constraints, and required45 behavior;46 - reproduction and regression expectations for bugs;47 - user/test impact, likely affected area, and related work where relevant.485. For UI/UX work, add the affected states, current and expected visual evidence,49 accessibility expectations, responsive/theme scope, and applicable design50 system components or tokens. Upload local screenshots and videos with51 `gh issue create --attach '<file>#<alt text>'` (or `gh issue edit` and52 `gh issue comment` with the same flag); never commit evidence media to the53 repository. Put non-media evidence such as probe output inside a collapsed54 `<details>` block.556. Choose only existing labels unless the user asks to create one.567. Show the proposed title, labels, and body unless the user waived review or57 automatic mode applies.588. End the issue body with this visually separate GitHub Note, replacing both59 values with the exact identities resolved for this run:6061 > [!NOTE]62 > Created on behalf of @username using ModelName.63649. Create the issue with the available GitHub tooling and return its URL.6566Lead with the outcome. Omit boilerplate, repeated summaries, and a narration of67the workflow.
frostney