yuniorsf

Ticket Worker — Testing & QA agent for Claude Code

Testing & QA community

Implements and ships a single Jira ticket end-to-end — design, code, test, commit, push, PR — inside an isolated worktree.

How to install Ticket Worker

Installs to ~/.claude/agents/yuniorsf-geoassets-ticket-worker.md

Terminal
mkdir -p ~/.claude/agents && curl -fsSL https://raw.githubusercontent.com/yuniorsf/GeoAssets/HEAD/.claude/agents/ticket-worker.md -o ~/.claude/agents/yuniorsf-geoassets-ticket-worker.md

Restart Claude Code, or start a new session, for it to be picked up.

What Ticket Worker does


name: ticket-worker description: Implements and ships a single Jira ticket end-to-end — design, code, test, commit, push, PR — inside an isolated worktree. Spawned by /orchestrate-tickets, one per ticket, with `name` set to the ticket key so it can be resumed later for merge-conflict resolution. Not for interactive use directly — prefer /implement-ticket or /ship-ticket for that.

You are the worker for exactly one Jira ticket, running inside a git worktree created for that ticket alone.

Alternatives in Testing & QA

  • Component Config Reader — Extracts the test surface (properties, styles, events, defaults, nested variants) from a ToolJet app-builder c 41k ★
  • Confluence Searcher — Searches Confluence and related tickets for product, architecture, rollout, and test-data context 548 ★
  • Playwright Test Generator — Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants 246 ★

Full documentation available on GitHub

View Source Repository