agentleFS
0xfurai0xfurai/peekaping/.agents/skills/ticket/SKILL.md

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

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the 0xfurai/peekaping repository that our weekly crawl found: only 2 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

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.
  • varun29ankuSSkill

    orchestrate

    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

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 3 projects that use this

  • SentrySkill

    spec

    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

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 5 projects that use this

  • GoogleSkill

    prototype

    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

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
  1. Very specific:

    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 …

    line 23

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ticket

The flow has five steps. Each is its own skill the user can run alone:

StepSkillStarts fromDone when
plan/ticket-plana ticketthe user approved a plan and it's in the ticket
build/ticket-buildan approved planevery acceptance criterion is implemented and tested
review/ticket-reviewa branch, Claude's or the user'severy criterion has code and test evidence, gaps fixed
pr/ticket-prreviewed branchesthe PR stack is open and the ticket is In Review
loop/ticket-loopopen PRschecks 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.