Skip to content

chore: add create-issue skill for filing Linear issues#24082

Merged
AztecBot merged 1 commit into
nextfrom
phil/create-issue-skill
Jun 17, 2026
Merged

chore: add create-issue skill for filing Linear issues#24082
AztecBot merged 1 commit into
nextfrom
phil/create-issue-skill

Conversation

@PhilWindle

Copy link
Copy Markdown
Collaborator

Summary

Adds a generic create-issue skill at .claude/skills/create-issue/SKILL.md for turning a unit of work into a well-formed Linear issue.

The skill encodes our conventions so issues are consistent and actionable:

  • Self-contained context — every issue must contain enough for a fresh agent (no prior conversation) to execute end-to-end: summary, evidence, root cause / approach with file:line references, the specific change, and references.
  • 1/2/3/5 point estimates — what each value means, with a reminder to state the reasoning so it can be overridden.
  • Required acceptance criteria — concrete, objectively checkable, including negative criteria.
  • Two modes — standalone (ask for team/project/labels/priority) vs. planning a project breakdown (inherit the project's conventions, link issues via parent/blocks/blockedBy).

Docs-only change (a Claude Code skill); no code or build impact.

Backport

Labeled backport-to-v5-next so the skill is also available on the v5 line.

## Summary

Adds a generic `create-issue` skill at `.claude/skills/create-issue/SKILL.md` for turning a unit of work into a well-formed Linear issue.

The skill encodes our conventions so issues are consistent and actionable:

- **Self-contained context** — every issue must contain enough for a fresh agent (no prior conversation) to execute end-to-end: summary, evidence, root cause / approach with `file:line` references, the specific change, and references.
- **1/2/3/5 point estimates** — what each value means, with a reminder to state the reasoning so it can be overridden.
- **Required acceptance criteria** — concrete, objectively checkable, including negative criteria.
- **Two modes** — standalone (ask for team/project/labels/priority) vs. planning a project breakdown (inherit the project's conventions, link issues via parent/`blocks`/`blockedBy`).

Docs-only change (a Claude Code skill); no code or build impact.

## Backport

Labeled `backport-to-v5-next` so the skill is also available on the v5 line.
@AztecBot AztecBot force-pushed the phil/create-issue-skill branch from 165f077 to 4993c78 Compare June 15, 2026 11:15
@AztecBot AztecBot added this pull request to the merge queue Jun 17, 2026
Merged via the queue into next with commit 6980e93 Jun 17, 2026
19 checks passed
@AztecBot AztecBot deleted the phil/create-issue-skill branch June 17, 2026 14:10
AztecBot added a commit that referenced this pull request Jun 17, 2026
## Summary

Adds a generic `create-issue` skill at
`.claude/skills/create-issue/SKILL.md` for turning a unit of work into a
well-formed Linear issue.

The skill encodes our conventions so issues are consistent and
actionable:

- **Self-contained context** — every issue must contain enough for a
fresh agent (no prior conversation) to execute end-to-end: summary,
evidence, root cause / approach with `file:line` references, the
specific change, and references.
- **1/2/3/5 point estimates** — what each value means, with a reminder
to state the reasoning so it can be overridden.
- **Required acceptance criteria** — concrete, objectively checkable,
including negative criteria.
- **Two modes** — standalone (ask for team/project/labels/priority) vs.
planning a project breakdown (inherit the project's conventions, link
issues via parent/`blocks`/`blockedBy`).

Docs-only change (a Claude Code skill); no code or build impact.

## Backport

Labeled `backport-to-v5-next` so the skill is also available on the v5
line.
@AztecBot

Copy link
Copy Markdown
Collaborator

✅ Successfully backported to backport-to-v5-next-staging #24153.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants