pickup
Skill5 starsChanged 44 days agoMITView on GitHub
User-invoked only. Assign the ticket, read it fully, brief the work, create the branch, start PROGRESS.md
- Reads credentials
33 other projects use a version of this.
Adopted by
Most recently taken up by
- fullstackhouse/skillstheir own version, first seen Nov 15, 2026
- jellydn/my-ai-toolstheir own version, first seen Nov 15, 2026
- tingyulu/MyR2D2their own version, first seen Nov 10, 2026
- seanmishra/claude-skillstheir own version, first seen Nov 6, 2026
- infenia/yuktatheir own version, first seen Nov 1, 2026
- zommuter/dotclaude-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use ai-review, discover and 10 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.
SkyWalker2506Skillai-review
This skill should be used when the user asks to "review a PR", "code review", "AI review", "check the pull request", or asks about automated review via OpenRouter or Gemma. Also activates when setting up GitHub Actions for PR review.
Also in 3 projects that use this
anombyte93Skilldiscover
Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.
Also in 3 projects that use this
asterkinSkilladr
Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.
Also in 3 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 5 projects that use this
Hugging FaceSkillimplement
Make tests pass. Invoke after /write-tests produces failing tests.
Also in 4 projects that use this
Microsoft AzureSkilldesign
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 3 projects that use this
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- jellydn/my-ai-tools★ 129same name
- dgilford/ai-science-toolkit★ 82same name
- oscabriel/skills★ 63same name
- lsnackerman/raw-clauding-skills★ 45same name
- iamneilroberts/claude-skills★ 26same name
- kaisa-kucherenko/claude-code-flow★ 24same name
- tingyulu/MyR2D2★ 20same name
- flurdy/agent-skills★ 9same name
- TimBroddin/skills★ 6same name
- keefar/ticket-flow★ 4same name
23 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 repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- assign-epicSkill
- briefingSkill
- bump-versionSkill
- captureSkill
- consultantSkill
- dependabot-reviewSkill
- fix-cicdSkill
- log-timeSkill
- morlockSkill
- morningSkill
- multi-repoSkill
- nightly-checkSkill
- pr-action-review-mine-loopSkill
- pr-action-reviewSkill
- pr-choreSkill
- pr-review-loopSkill
- prSkill
- pushSkill
- qa-review-actionSkill
- refineSkill
- runSkill
- syncSkill
- wrap-upSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
24 rules. 0 are common, 9 are distinctive, and 15 are very specific to this project.
0
Common
Most of the 29 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
15
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Ticket input: use the value and flags supplied with the skill invocation.
- Very specific: line 22
If --stay is present anywhere in the invocation input, enable stay mode and remove the flag before normalising.
- Very specific: line 23
If --qa is present anywhere in the invocation input, enable QA-rework mode and remove the flag before normalising.
- Very specific: line 25
If the remaining ticket ID is a bare number (e.g.
- Very specific: line 30
Check that JIRA_BASE_URL, JIRA_API_TOKEN, JIRA_EMAIL, and JIRA_ACCOUNT_ID are set in .env.
- Distinctive: line 55
Check the fetched ticket data:
- Very specific: line 57
If fields.parent is present and its issuetype is "Epic", the epic is set → continue to Step 3.
- Very specific: line 58
If fields.customfield_10014 is set (classic epic link field), the epic is set → continue to Step 3.
- Distinctive: line 59
If neither is set → note this in the brief (Step 9) as an open question, then continue.
- Very specific: line 63
If fields.assignee is null (unassigned) → proceed.
- Very specific: line 64
If fields.assignee.accountId matches $JIRA_ACCOUNT_ID → proceed.
- Very specific: line 65
If fields.assignee is someone else → STOP.
- Distinctive: line 78
Do this before the In Progress transition (Step 6).
- Distinctive: line 123
Read and summarise each subtask's summary, description, and status.
- Very specific: line 127
If the ticket has a fields.parent, fetch that ticket too to understand the broader story or epic.
- Very specific: line 129
If fields.customfield_10014 (epic link) is set and different from the parent, fetch that as well.
- Distinctive: line 167
Run git branch --show-current to check the current branch.
- Very specific: line 168
If the current branch is main (or empty/detached), STOP and tell the user: "You are on main.
- Distinctive: line 174
If the merge reports conflicts, STOP and ask the user to resolve them before continuing.
- Very specific: line 175
Every commit for this ticket must reference the new ticket ID in its message (e.g.
- Distinctive: line 184
Use the ticket ID lowercased and a 2–4 word kebab-case description derived from the summary.
- Very specific: line 188
Create a PROGRESS.md file in the repo root as the session scratchpad (per AGENTS.md).
- Very specific: line 213
If stay mode (
--stay) is NOT active: create PROGRESS.md fresh. If one already exists (leftover from a previous session), read it first, … - Distinctive: line 252
After the briefing is output, the branch is created (or confirmed, in stay mode), and PROGRESS.md is initialised (or appended to):
“Common” is measured: kept by at least 6 in 10 of the 29 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
Pick up a Jira ticket: assign it to me, move it to In Progress, read it fully with all subtasks and linked context, then prepare to implement.
Ticket input: use the value and flags supplied with the skill invocation.
Usage: pickup <ticket-id> [--stay] [--qa]
--stay— do not create a new branch. Stay on the current branch and do the work there. Use this when stacking multiple tickets on one branch.--qa— QA-rework mode. Work is already done and merged tomain; the ticket is back from QA with comments. Runs the normal Jira front-door (assign, In Progress, board) — whichqa-review-actiondoesn't — then hands off toqa-review-actionfor the feedback itself. Branch behaves like a normal pickup (fresh fix branch offmain); add--stayto rework on the current branch with latestmainmerged in first.
Step 0 — Parse arguments and normalise the ticket ID
Split the invocation input into the ticket ID and any flags:
- If
--stayis present anywhere in the invocation input, enable stay mode and remove the flag before normalising. Stay mode changes Steps 10 and 11 only — all Jira steps run unchanged. - If
--qais present anywhere in the invocation input, enable QA-rework mode and remove the flag before normalising. QA-rework mode is described in Step 12 — all Jira steps (1–8) and the PROGRESS.md step (11) run unchanged; Step 9 adds one conditional brief line. --stayand--qacan be combined. With both active, you do the QA rework on the current branch (stay mode) and Step 10 merges latestmaininto it first.- If the remaining ticket ID is a bare number (e.g.
25), prepend$JIRA_PROJECT_KEY-to get e.g.PROJ-25. - Store the cleaned, normalised ticket ID as
TICKET_KEY. UseTICKET_KEYfor all subsequent steps.
Step 1 — Verify credentials
Check that JIRA_BASE_URL, JIRA_API_TOKEN, JIRA_EMAIL, and JIRA_ACCOUNT_ID are set in .env. If any are missing, stop and ask the user to add them. Source .env before all Jira API calls.
Step 2 — Fetch the ticket
source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
"$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY?expand=subtasks,renderedFields"Parse the response and extract:
fields.summaryfields.description(full rendered text)fields.assignee(may be null)fields.status.namefields.issuetype.namefields.parent(if present — epic or story)fields.subtasks(array of subtask keys)fields.issuelinks(linked issues)fields.labelsfields.priority.namefields.customfield_10014(epic link, if present)
Step 2a — Check epic assignment
Check the fetched ticket data:
- If
fields.parentis present and its issuetype is "Epic", the epic is set → continue to Step 3. - If
fields.customfield_10014is set (classic epic link field), the epic is set → continue to Step 3. - If neither is set → note this in the brief (Step 9) as an open question, then continue.
Step 3 — Assignee safety check
- If
fields.assigneeis null (unassigned) → proceed. - If
fields.assignee.accountIdmatches$JIRA_ACCOUNT_ID→ proceed. - If
fields.assigneeis someone else → STOP. Output: "$TICKET_KEY is assigned to [displayName] — are you sure you want to pick this up?" Do not proceed until the user confirms.
Step 4 — Assign the ticket to me
source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
-X PUT "$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY/assignee" \
-H "Content-Type: application/json" \
-d "{\"accountId\": \"$JIRA_ACCOUNT_ID\"}"Step 5 — Move onto the active board
Do this before the In Progress transition (Step 6). Adding an issue to the board drops it into the board's default column (e.g. "Ready for Development"), which would overwrite an In Progress status set beforehand. Always add to the board first, then transition last.
source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
-X POST "$JIRA_BASE_URL/rest/agile/1.0/board/$JIRA_BOARD_ID/issue" \
-H "Content-Type: application/json" \
-d "{\"issues\": [\"$TICKET_KEY\"]}"Step 6 — Move to In Progress
This must be the last Jira write, so nothing (like the board-add above) can clobber the status afterwards.
First, get available transitions (fetch them fresh — available transitions and their ids depend on the ticket's current status, so never reuse an id from an earlier run):
source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
"$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY/transitions"Find the transition whose name matches "In Progress" (case-insensitive). Use its id to apply it:
source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
-X POST "$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY/transitions" \
-H "Content-Type: application/json" \
-d '{"transition": {"id": "<transition-id>"}}'Then confirm the status actually landed on In Progress (a 204 only means the request was accepted, not that the status stuck):
source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
"$JIRA_BASE_URL/rest/api/3/issue/$TICKET_KEY?fields=status"Step 7 — Fetch all subtasks
For each key in fields.subtasks, fetch the full issue:
source .env && curl -s -u "$JIRA_EMAIL:$JIRA_API_TOKEN" \
"$JIRA_BASE_URL/rest/api/3/issue/<subtask-key>?expand=renderedFields"Read and summarise each subtask's summary, description, and status.
Step 8 — Fetch parent/epic context
If the ticket has a fields.parent, fetch that ticket too to understand the broader story or epic.
If fields.customfield_10014 (epic link) is set and different from the parent, fetch that as well.
Step 9 — Output a brief
Print a structured briefing so the work is clear before any code is written:
## Ticket: $TICKET_KEY — <summary>
**Type:** <issuetype>
**Priority:** <priority>
**Status:** → In Progress (just moved)
**Parent:** <parent key + summary, if any>
**Branch (stay mode only):** <current branch — include this line only when `--stay` is active; omit otherwise>
**🔁 QA rework:** <only include this line when `--qa` is active — "Work is already merged to `main`. This is rework from QA comments. After branch setup, control hands off to `qa-review-action` to classify and action the feedback.">
### Description
<rendered description>
### Subtasks
- [ ] <subtask-key>: <summary> (<status>)
...
### Linked issues
- <link type>: <key> — <summary>
...
### Implementation notes
<what needs to be built, based on reading the ticket and relevant docs>
### Open questions
<anything unclear that needs resolving before coding starts>Step 10 — Create the feature branch (skipped in stay mode)
If stay mode (--stay) is active:
- Run
git branch --show-currentto check the current branch. - If the current branch is
main(or empty/detached), STOP and tell the user: "You are onmain. The--stayflag is for continuing work on an existing feature branch. Rerun without--stayto create a new branch, or switch to the feature branch first." - Otherwise: do not switch branches, do not checkout main, do not create a new branch. All work happens on the current branch.
- If both
--qaand--stayare active: bring the merged implementation into the current branch first so the QA fixes land on top of it:
If the merge reports conflicts, STOP and ask the user to resolve them before continuing. Do not proceed to the hand-off with an unfinished merge.git fetch origin main && git merge origin/main - Every commit for this ticket must reference the new ticket ID in its message (e.g.
$TICKET_KEY: feat: ...), even though the branch name references a different ticket. - Skip to Step 11.
Otherwise, following CONTRIBUTING.md naming conventions, create and switch to a new branch:
git checkout main && git pull && git checkout -b <ticket-id-lowercase>-<short-description>Use the ticket ID lowercased and a 2–4 word kebab-case description derived from the summary.
Step 11 — Initialise PROGRESS.md
Create a PROGRESS.md file in the repo root as the session scratchpad (per AGENTS.md). Seed it with the ticket context so the session log starts with a clear baseline:
# PROGRESS.md — <ticket-id>: <summary>
**Branch:** <branch-name>
**Started:** <today's date>
## Plan
<high-level implementation approach derived from the ticket brief>
## Progress
_Nothing logged yet._
## Decisions
_None yet._
## Open Questions
<carry over any open questions from the Step 9 brief>If stay mode (--stay) is NOT active: create PROGRESS.md fresh. If one already exists (leftover from a previous session), read it first, then overwrite it with the new session header — do not append to stale content.
If stay mode (--stay) is active and a PROGRESS.md already exists, it belongs to the branch's ongoing work — do not overwrite it. Instead, append a new ticket section to the end:
---
# <ticket-id>: <summary> (stacked on this branch)
**Branch:** <current branch>
**Started:** <today's date>
## Plan
<high-level implementation approach derived from the ticket brief>
## Progress
_Nothing logged yet._
## Decisions
_None yet._
## Open Questions
<carry over any open questions from the Step 9 brief>If stay mode (--stay) is active and PROGRESS.md does NOT exist, create it fresh using the standard template above (same as non-stay mode).
Step 12 — Hand off to QA review (QA-rework mode only)
Only when --qa is active (otherwise skip). The Jira front-door (assign, In Progress, board) and branch are now set up — the state qa-review-action can't establish on its own.
Tell the user: "Ticket set up for QA rework — assigned, In Progress, on branch <branch-name>. Handing off to qa-review-action." Then read and follow .agents/skills/qa-review-action/SKILL.md for $TICKET_KEY to fetch, classify, and action the feedback. Don't duplicate that work here.
After the briefing is output, the branch is created (or confirmed, in stay mode), and PROGRESS.md is initialised (or appended to):
- In QA-rework mode (
--qa): proceed straight to Step 12 — do not pause for go-ahead, sinceqa-review-actionhas its own confirmation gates before applying fixes or posting to Jira. - Otherwise: pause and ask: "Ready to start — any questions before I begin?" Wait for the user's go-ahead before writing any code.
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.

