ticket-pr
Skill1.2k starsChanged 16 days agoMITView on GitHub
Open a ticket's reviewed branches as a PR stack and move the ticket to In Review.
Trending
More talk lately.thin dataabout the whole repository
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.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- releaseSkill
- ticket-buildSkill
- ticket-loopSkill
- ticket-planSkill
- ticket-reviewSkill
- ticketSkill
- treehouseSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 22
Run alone, end by telling the user the next step: /ticket-loop <PP-n>.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ticket: PR
Start with setup.
Open the stack
The stack is the plan's PR stack, or without a plan, the ticket's branches as they are: one branch, one PR. Ask before splitting commits the user wrote.
An agent (DELEGATE.md) pushes and opens the PRs bottom up, with the title format and body template in STACK.md, and reports the PR numbers. Its brief carries the branch list, the ticket's Linear URL, and the evidence for each criterion, from the review's table when you have it. A branch that already has a PR keeps it; the agent updates its body if the stack around it changed.
Then in Linear: file the follow-ups from the plan or the review as tickets, after the duplicate check in docs/agents/issue-tracker.md. Move the ticket to In Review, add each PR as a link, and comment the stack.
Done when: every PR is open with the right base, title and body, and the ticket is In Review with the PRs linked.
Run alone, end by telling the user the next step: /ticket-loop <PP-n>.
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.

