jira
Manage Jira issues, boards, sprints, and projects via the jira-cli. Search, create, update, and transition issues directly from the command line.
Packaged view
This page reorganizes the original catalog entry around fit, installability, and workflow context first. The original raw source lives below.
Install command
npx @skill-hub/cli install jdrhyne-agent-skills-jira
Repository
Skill path: skills/jira
Manage Jira issues, boards, sprints, and projects via the jira-cli. Search, create, update, and transition issues directly from the command line.
Open repositoryBest for
Primary workflow: Ship Full Stack.
Technical facets: Full Stack.
Target audience: everyone.
License: Unknown.
Original source
Catalog source: SkillHub Club.
Repository owner: jdrhyne.
This is still a mirrored public skill entry. Review the repository before installing into production workflows.
What it helps with
- Install jira into Claude Code, Codex CLI, Gemini CLI, or OpenCode workflows
- Review https://github.com/jdrhyne/agent-skills before adding jira to shared team environments
- Use jira for development workflows
Works across
Favorites: 0.
Sub-skills: 0.
Aggregator: No.
Original source / Raw SKILL.md
---
name: jira
description: Manage Jira issues, boards, sprints, and projects via the jira-cli. Search, create, update, and transition issues directly from the command line.
homepage: https://github.com/ankitpokhrel/jira-cli
metadata: {"clawdbot":{"emoji":"🎫","requires":{"bins":["jira"]},"install":[{"id":"brew","kind":"brew","formula":"jira-cli","bins":["jira"],"label":"Install jira-cli (brew)"}]}}
---
# jira
Use `jira` to manage Jira issues, sprints, and boards. Requires API token setup.
## Setup (once)
1. Generate an API token: https://id.atlassian.com/manage-profile/security/api-tokens
2. Export it: `export JIRA_API_TOKEN="your-token"` (add to ~/.zshrc for persistence)
3. Initialize: `jira init --server https://your-org.atlassian.net --login [email protected] --installation cloud`
## Common commands
### Issues
- List issues: `jira issue list -p PROJECT`
- View issue: `jira issue view PROJ-123`
- Create issue: `jira issue create -p PROJECT -t "Task" -s "Summary" -b "Description"`
- Edit issue: `jira issue edit PROJ-123 -s "New summary"`
- Assign issue: `jira issue assign PROJ-123 "[email protected]"`
- Transition issue: `jira issue move PROJ-123 "In Progress"`
- Comment: `jira issue comment add PROJ-123 "My comment"`
- Search (JQL): `jira issue list -q "project = MKT AND status = 'To Do'"`
### Sprints
- List sprints: `jira sprint list -p PROJECT`
- View active sprint: `jira sprint list -p PROJECT --state active`
- Sprint issues: `jira sprint list -p PROJECT --state active --plain`
### Boards
- List boards: `jira board list -p PROJECT`
### Epics
- List epics: `jira epic list -p PROJECT`
- View epic: `jira epic view PROJ-100`
### Projects
- List projects: `jira project list`
## Output formats
- `--plain` — Tab-separated, no colors (best for scripting)
- `--columns key,summary,status` — Select columns
- `--no-truncate` — Don't truncate long fields
## Tips
- Set default project in config: `~/.config/.jira/.config.yml`
- Use JQL for complex queries: `-q "assignee = currentUser() AND status != Done"`
- Open in browser: `jira open PROJ-123`
## Notes
- Confirm with user before creating/editing/transitioning issues
- For bulk operations, show what will change before executing