Implement Jira Issue

Description

This Claude Code command automates the complete workflow of implementing a Jira issue - from fetching and analysing the issue details to making code changes, writing tests, and updating the ticket status. It provides a streamlined, git-integrated approach with emphasis on TDD and proper workspace management.

I have this stored at ~/.claude/commands/jira/implement.md, which then translates to the following command in Claude Code.

/jira:implement [jira-id]

This prompt is best used with the following frontmatter:

---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*), Bash(git checkout:*), Bash(git push:*), Bash(git pull:*)
description: Implement JIRA issue
argument-hint: [jira-id]
---

Context

Current git status: !git status
Current git diff (staged and unstaged changes): !git diff HEAD
Current branch: !git branch --show-current
Recent commits: !git log --oneline -10
Jira Issue: $ARGUMENTS

Steps to undertake

Fetch & Analyse – Use mcp-atlassian; extract Summary, Description, Acceptance Criteria, Type, Priority, Labels, Comments.
Understand Requirements – Identify core change, constraints, dependencies. Clarify ambiguity, assumptions, and edge cases.
Prepare Workspace. Check for uncommitted changes and clarify with me what to do with them. Go to default branch, update, then:

git checkout -b feature/rlew-<TICKET>-<short-desc>

Plan Implementation – Files to change, changes per file, new files, test updates, edge cases. Confirm before coding.
Tests – Add/update for happy paths, edge cases, errors, integrations. TDD approach.
Implement – Follow style, add docs/comments, handle errors, consider performance.
Verify – All checks pass, format Markdown with Prettier (run tests, linting)
Suggest commit message and confirm with me before committing:

<jira-id>: <brief-description>

- change 1
- change 2
- tests added

Update Jira – Comment with changes, testing, notes; transition status if needed.
Summary – Changes, tests, remaining work, review focus.