A JIRA ticket start workflow that assigns the ticket, updates its status, creates a feature branch, checks for backporting, and loads project guidance. JIRA is a system for tracking planned engineering work.

Use it when beginning work on a JIRA ticket, including authenticating tools, viewing and assigning the ticket, creating the branch, and loading area-specific instructions.

It gathers the ticket and repository context before coding and helps keep the branch and ticket state aligned. It also flags when a change must later be applied to another release.

start — Skill for Claude Code by quay

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/quay/ai-helpers

agentmods

npx agentmods add skills/quay/ai-helpers/start

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 16 skills, 1 command.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/quay/ai-helpers/start.svg)](https://agentmods.dev/skills/quay/ai-helpers/start)

Your own site

<a href="https://agentmods.dev/skills/quay/ai-helpers/start"><img src="https://agentmods.dev/badge/skills/quay/ai-helpers/start.svg" alt="Measured on agentmods" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 620 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00041	$0.00620
Opus 5	$0.00020	$0.00310
Sonnet 5	$0.00008	$0.00124
Haiku 4.5	$0.00004	$0.00062

Measured 2d ago against content hash 1dfbc02bd4af, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

start scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/dev/skills/start/SKILL.md · 86 lines

What it actually says

Start Work on JIRA Ticket

Begin work on JIRA ticket $ARGUMENTS.

Step 0: Session Bootstrap

bash .claude/scripts/session-setup.sh

Handles acli install+auth, recommended hooks, pre-commit, and gh auth check. Runs once per session (skips on subsequent calls).

Step 1: View and Assign

bash .claude/scripts/jira-ops.sh view $ARGUMENTS

Review the ticket summary, status, and description. Then assign and transition:

bash .claude/scripts/jira-ops.sh assign $ARGUMENTS
bash .claude/scripts/jira-ops.sh transition $ARGUMENTS "ASSIGNED"

Step 2: Check Backport Requirement

bash .claude/scripts/jira-ops.sh check-version $ARGUMENTS

If Target Version is set, backporting is required after merge.

Step 3: Create Branch

DEFAULT_BRANCH="${PRIMARY_BRANCH:-$(git rev-parse --abbrev-ref origin/HEAD 2>/dev/null | sed 's|origin/||')}"
DEFAULT_BRANCH="${DEFAULT_BRANCH:-master}"
git checkout "$DEFAULT_BRANCH" && git pull origin "$DEFAULT_BRANCH"
git checkout -b $ARGUMENTS-short-description

Branch naming: <TICKET-KEY>-<kebab-case-description>. Derive the description from the ticket summary. Ask the user if it's ambiguous.

Step 4: Load Context

Based on the ticket's area, read the relevant docs. The doc mapping is project-specific — check the project's AGENTS.md for the area-to-doc table.

Common patterns:

Area	Doc
API endpoints, auth	`agent_docs/api.md`
Database, migrations	`agent_docs/database.md`
Testing	`agent_docs/testing.md`
Architecture	`agent_docs/architecture.md`
Frontend	`web/AGENTS.md` or equivalent

Step 5: Report

Summarize:

Ticket: key, summary, status, assignee
Backport: required or not
Branch: name created
Docs loaded
Next step: /code

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 86 lines · 41 tokens per session scan A 1dfbc02bd4af

Subscribe to this mod's changes

start is a skill published in the GitHub repository quay/ai-helpers (3 stars, last pushed 19d ago), licensed MIT. It adds 41 tokens to every session and 620 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Git and workflow Project management

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…

vybestack/llxprt-code · 87 tokens

cyrus-setup-repository

Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.

cyrusagents/cyrus · 25 tokens

github-sync

Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.

a5c-ai/babysitter · 0 tokens

github-sync-helper

General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…

OpenMinis/MinisSkills · 124 tokens