# ticket

A command that handles the full ticket workflow: fetch task details from JIRA or Linear, explore related code, implement changes, and create a linked PR. Reduces manual sync between issue tracker and repository.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 6091 repo stars
- Author: ChrisWiles
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/ChrisWiles/claude-code-showcase/tree/HEAD/.claude/commands/ticket.md
- Updated: 2026-01-06
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/ticket

## What it does

Running the command fetches ticket metadata via JIRA or Linear MCP tools—title, description, acceptance criteria, and comments. It searches the codebase for related files, creates a branch following naming conventions, and guides you through implementation with test-first practices.

As work progresses, the command updates the ticket status, posts progress comments, and flags blockers. Once changes are ready, it creates a pull request with `gh pr create`, links it to the ticket, and includes the ticket ID in the commit message.

The command requires active MCP connections to JIRA, Linear, or GitHub; access to `git` and `gh` CLI tools; and project configuration files in the expected locations. If an unrelated bug surfaces during work, it can create a separate ticket and cross-link it.

## Requirements
- Works with: Jira, Linear

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/ticket.md` — Call it with /ticket. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/ticket.md` — Call it with /prompts:ticket. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/ticket.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/ticket.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/ChrisWiles/claude-code-showcase/tree/HEAD/.claude/commands/ticket.md

## When to use it
- move from ticket to pull request without manual status switching
- gather full requirements and context from comments and descriptions
- identify all files that need changes for a given task
- keep ticket status in sync with development progress

## Example prompts
- /ticket PROJ-123
- /ticket INFRA-456
- /ticket Linear-team/task-789

## Similar
- [ticket-craft](https://affpapa.org/en/nevibecode/skills/ticket-craft.md) — skill · 283 installs
- [SHIP](https://affpapa.org/en/nevibecode/mcp/ship.md) — MCP server
- [track-findings](https://affpapa.org/en/nevibecode/skills/track-findings.md) — skill · 26 installs
- [team-workflow](https://affpapa.org/en/nevibecode/skills/team-workflow.md) — skill · 2400 installs
- [project-management](https://affpapa.org/en/nevibecode/skills/project-management.md) — skill · 399 installs
- [log](https://affpapa.org/en/nevibecode/commands/log.md) — command · 351 installs

From the same set: [chriswiles/claude-code-showcase](https://affpapa.org/en/nevibecode/by/chriswiles/claude-code-showcase.md) — 11 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
