Jira Skill for Claude Code

Comprehensive Jira issue management skill for Red Hat’s issues.redhat.com, integrated with your Nix configuration and org-mode workflow.

Overview

This skill provides full command-line access to Jira issues through the jira-cli tool, with automatic API token injection from passage and integration with your existing workflow (TODOs, Git).

Installation

Already configured! The skill is located at:

~/.config/claude/skills/Jira/

The jira command is wrapped with your API token automatically via Nix configuration in /home/vincent/src/home/systems/kyushu/home.nix.

Structure

Jira/
├── skill.md              # Main skill definition
├── README.md             # This file
├── workflows/            # Workflow guides
│   ├── View.md           # View issue details
│   ├── List.md           # List and filter issues
│   ├── Create.md         # Create new issues
│   ├── Update.md         # Update issue fields
│   ├── Comment.md        # Add comments
│   ├── Search.md         # Advanced JQL searches
│   └── Transition.md     # Workflow state changes
└── tools/                # Helper scripts
    └── jira-search       # Common search patterns

Quick Start

View an Issue

jira issue view SRVKP-7327

List Your Issues

jira issue list -a $(jira me) -s ~Done

Create an Issue

jira issue create

Search with JQL

jira issue list --jql "project = SRVKP AND status = 'To Do' ORDER BY priority DESC"

Workflows

1. View Workflow

Trigger: User mentions issue key or asks to view issue Purpose: Display detailed issue information Example: “Show me SRVKP-7327”

2. List Workflow

Trigger: “list my issues”, “show tickets”, etc. Purpose: Filter and display multiple issues Example: “Show my open bugs”

3. Create Workflow

Trigger: “create issue”, “file bug”, “new task” Purpose: Create new Jira issues Example: “Create a bug for the pod creation issue”

4. Update Workflow

Trigger: “assign to”, “change priority”, “add label” Purpose: Modify issue fields Example: “Assign SRVKP-1234 to me”

5. Comment Workflow

Trigger: “add comment”, “comment on” Purpose: Add discussion to issues Example: “Comment that I’m working on it”

6. Search Workflow

Trigger: “search for”, “find issues”, complex filtering Purpose: Advanced JQL queries Example: “Find stale high priority issues”

7. Transition Workflow

Trigger: “start work”, “mark done”, “move to” Purpose: Change workflow states Example: “Move SRVKP-1234 to In Progress”

Helper Tools

jira-search

Predefined search patterns for common queries:

# My open issues
jira-search my-open

# My work in progress
jira-search my-progress

# Unassigned team bugs
jira-search team-bugs

# Stale issues
jira-search stale

# High priority items
jira-search high-priority

Available patterns:

my-open - Your open issues
my-progress - Your in-progress work
my-week - Updated this week
my-blocked - Your blocked issues
team-bugs - Unassigned bugs
team-blocked - All blocked issues
stale - No updates in 30+ days
high-priority - Critical/High/Blocker items
needs-review - In code/QE review

Integration with Other Skills

TODOs Skill

Create org-mode TODOs from Jira issues:

View issue details
Extract key information
Create TODO in todos.org
Link back to Jira issue

Git Skill

Reference issues in commits:

git commit -m "fix: Resolve pod creation issue

Fixes SRVKP-7327"

Email Skill

Share issue summaries with team

Common Use Cases

Daily Standup Prep

# What did I do yesterday?
jira-search my-week --plain

# What am I doing today?
jira-search my-progress

Bug Triage

# Unassigned bugs by priority
jira-search team-bugs --plain

# Assign to yourself
jira issue assign SRVKP-1234 $(jira me)

Sprint Planning

# High priority items not in sprint
jira issue list --jql "priority IN (Critical, High) AND sprint is EMPTY"

# Add to sprint
jira sprint add SPRINT-123 SRVKP-1234

Investigation Workflow

# 1. View issue
jira issue view SRVKP-7327

# 2. Start work
jira issue assign SRVKP-7327 $(jira me)
jira issue move SRVKP-7327 "In Progress"

# 3. Update Jira with findings
jira issue comment add SRVKP-7327 "Root cause identified: [details]"

# 4. Complete
jira issue move SRVKP-7327 "Code Review"

Configuration

Jira Config

Located at: ~/.config/.jira/.config.yml

Key settings:

server: https://issues.redhat.com
installation: local
auth_type: bearer
project.key: SRVKP (default)

API Token

Managed via passage, automatically injected by Nix wrapper:

passage show redhat/issues/atlassian/token

Wrapper Location

/home/vincent/src/home/systems/kyushu/home.nix:

jira-wrapped = pkgs.writeShellScriptBin "jira" ''
  export JIRA_API_TOKEN=$(${pkgs.passage}/bin/passage show redhat/issues/atlassian/token)
  exec ${pkgs.jira-cli-go}/bin/jira "$@"
'';

Best Practices

Always Use –plain for Processing

jira issue view ISSUE-KEY --plain

Document State Changes

jira issue move ISSUE-KEY "Done"
jira issue comment add ISSUE-KEY "Completed: [details]"

Reference issue keys in commits
Link PRs in Jira comments

Use Consistent Labels

documentation - Needs docs
release-notes-pending - User-facing changes
customer-reported - From customers
test-req - Needs tests

Save Common Queries

Document frequently-used JQL queries in notes

Tips & Tricks

Alias common commands:

alias jira-mine='jira issue list -a $(jira me) -s ~Done'
alias jira-todo='jira issue list -a $(jira me) -s "To Do"'

Combine with shell tools:

# Count my issues
jira-search my-open --plain | wc -l

# Extract issue keys
jira-search team-bugs --plain | awk '{print $1}'

Batch operations:

# Add label to multiple issues
for issue in SRVKP-{1..5}; do
  jira issue edit "$issue" --label +urgent
done

Use currentUser(): Always use $(jira me) or currentUser() instead of hardcoding usernames
Relative dates: Use -7d, startOfWeek() instead of specific dates

Troubleshooting

API Token Issues

# Verify token
passage show redhat/issues/atlassian/token

# Test connection
jira me

# Check config
cat ~/.config/.jira/.config.yml

Permission Errors

Ensure you’re on Red Hat VPN
Verify project access in web UI
Check API token scopes

No Results

Verify project key
Check filter criteria
Try with –debug flag
Use web UI to test JQL

Resources

Jira CLI Documentation: https://github.com/ankitpokhrel/jira-cli
Red Hat Jira: https://issues.redhat.com
JQL Reference: https://issues.redhat.com/secure/JiraJQLHelp.jspa
Skill Location: ~/.config/claude/skills/Jira/

Examples

Complete Workflow Example

# Morning standup
jira-search my-progress

# Find work
jira-search team-bugs --limit 5

# Assign and start
jira issue assign SRVKP-1234 $(jira me)
jira issue move SRVKP-1234 "In Progress"

# Work on it...
# (Make code changes, test)

# Update Jira
jira issue comment add SRVKP-1234 "Fix implemented in PR #123"
jira issue move SRVKP-1234 "Code Review"

# End of day
jira-search my-week --plain > ~/standup-notes.txt

Future Enhancements

Possible additions:

Sprint management workflows
Epic management workflows
Bulk operations tools
Dashboard generation
Report generation
Metrics and analytics
Custom field support
Attachment handling
Time tracking workflows

Contributing

To add new workflows:

Create workflow file in workflows/
Update skill.md workflow routing table
Document in this README
Test with real Jira issues

To add new tools:

Create script in tools/
Make executable: chmod +x tools/script-name
Document usage in this README
Add examples

License

This skill configuration is part of your personal NixOS configuration.