Skill11.8k repo starsupdated today

ticket-format

The ticket-format skill provides a standardized three-section template for creating Linear or Superset tickets in the superset-sh/superset repository. Use it when drafting or grooming tickets to ensure consistent structure: a context section explaining the problem or feature request, an optional references section tracking the ticket's origin, and implementation notes with optional subsections for files, approach, related code patterns, and known constraints. This enforces outcome-focused communication and enables progressive detail as codebase context becomes available.

View source Repository: superset

Install in Claude Code

Copy

git clone --depth 1 https://github.com/superset-sh/superset /tmp/ticket-format && cp -r /tmp/ticket-format/.agents/skills/ticket-format ~/.claude/skills/ticket-format

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# Ticket Format

## Context
2–4 sentences. What's broken or wanted, and why. Outcome-focused, not solution-focused.

## References
Where the ticket came from. Omit section if none.

| Source | Who | Link | Date |
|--------|-----|------|------|
| Slack #feedback | @alice | [thread](…) | 2026-05-10 |

## Implementation notes
Agent-groomed. Leave empty if you don't have codebase context — a later grooming pass will fill it in. When you do fill it in, use these sub-headings and skip what doesn't apply:

- `### Files` — `path:line` + why relevant
- `### Approach` — one paragraph
- `### Related code` — similar patterns in the repo
- `### Gotchas` — constraints, prior incidents