ticket
Skill1.2k starsChanged 16 days agoMITView on GitHub
Work a Linear ticket (PP-<n>) through the team flow: plan with the user, build with tests, review against the ticket, open a PR stack, and loop on CI and review comments until merged. Use when the user hands over a ticket, or asks to run part of the flow for one: plan it, review their own branch, open its PRs, or handle its PR comments.
23 other projects use a version of this.
Trending
More talk lately.thin dataabout the whole repository
Most recently taken up by
- infenia/yuktatheir own version, first seen Nov 8, 2026
- peterpme/skillstheir own version, first seen Nov 8, 2026
- Mrbaeksang/skillstheir own version, first seen Nov 8, 2026
- kyle-chalmers/ticketwrighttheir own version, first seen Nov 8, 2026
- codingpains/skillstheir own version, first seen Nov 1, 2026
- philippmossier/cofabriqtheir own version, first seen Nov 1, 2026
Who's talking about 0xfurai/peekaping
- A Hacker News story“peekaping: selfhosted uptime monitoring similar to UptimeKuma (Go/React)”Hacker News · Sep 8, 2025 · 4 points
- ProSkillsMD/proskills“[Candidate] 0xfurai/peekaping/.agents/skills/ticket-review - ticket-review”GitHub · Oct 26, 2026
The biggest 2 of 2 mentions linking to the repository that our crawl found. Each line is their own headline.
Used with
Projects with it also use orchestrate, retro and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
varun29ankuSSkillorchestrate
This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
Also in 4 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 3 projects that use this
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 5 projects that use this
GoogleSkillprototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- kjnez/claude-code-django★ 177same name
- peterpme/skills★ 28same name
- ConnorGriffin/skills★ 21same name
- kyle-chalmers/ticketwright★ 4same name
- a-saven/agent-skills★ 2same name
- AaravChadha/acstack★ 2same name
- gingerminds/claude-skills★ 2same name
- Mrbaeksang/skills★ 2same name
- codingpains/skills★ 1same name
- HoussemDjeghri/self-review★ 1same name
13 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- releaseSkill
- ticket-buildSkill
- ticket-loopSkill
- ticket-planSkill
- ticket-prSkill
- ticket-reviewSkill
- treehouseSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Run SETUP.md once. Then for each step, read its skill file, ../ticket-<step>/SKILL.md next to this skill's folder, and follow it, skipping …
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ticket
The flow has five steps. Each is its own skill the user can run alone:
| Step | Skill | Starts from | Done when |
| plan | /ticket-plan | a ticket | the user approved a plan and it's in the ticket |
| build | /ticket-build | an approved plan | every acceptance criterion is implemented and tested |
| review | /ticket-review | a branch, Claude's or the user's | every criterion has code and test evidence, gaps fixed |
| pr | /ticket-pr | reviewed branches | the PR stack is open and the ticket is In Review |
| loop | /ticket-loop | open PRs | checks green and every comment handled, then on until merged |
/ticket <target> runs all five in order. /ticket <target> from <step> starts at that step and runs to the end: from review after the user implemented it themselves, from loop once the PRs are open. Without from, when work already exists, start at the first step whose done-when doesn't hold.
Setup marks the ticket In Progress when work on it starts; only the pr step moves it on, to In Review.
Run SETUP.md once. Then for each step, read its skill file, ../ticket-<step>/SKILL.md next to this skill's folder, and follow it, skipping its setup line and its closing "run alone" line. Move on when its done-when holds.
The plan step's checkpoint is the one place the flow waits for the user, besides a later step that breaks the plan.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

