c-jira — Claude Code skill: what it does, how to install
Manages Jira tickets from the terminal using jira-cli. Helps list issues, transition workflow statuses, and update sprints without opening a browser.
npx skills add daxaur/openpaw --skill c-jira -a claude-codeWhat c-jira does
This skill teaches your assistant how to execute Jira operations through the jira command-line tool. It lists issues filtered by project, status, or type, creates new tickets with assigned priorities and labels, submits comments, and tracks sprint allocations. It also tells the agent to search for duplicate tickets before creating a new one.
For workflow transitions, the agent invokes jira issue move. It inspects allowed status names via jira issue view first, ensuring transitions match your workflow. Full issue keys like MYPROJ-123 are passed to all underlying commands.
The CLI binary is required on your machine. You need to install it via brew install ankitpokhrel/jira-cli/jira-cli and run jira init to configure the instance URL and credentials beforehand.
What it helps with
- Create tickets with labels, priorities, and descriptions from the CLI
- Move issues between workflow states like In Progress or Done
- Inspect assigned Jira tasks with project and type filters
- Add status comments and assign tasks to sprint numbers
Example prompts for the agent
- List all high-priority bugs assigned to me in the PROJ board
- Create a bug ticket in MYPROJ about login errors and tag it backend
- Move MYPROJ-123 to In Review and comment that fix is ready
How to install c-jira
1Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-jira -a claude-code2Manually: put the files in place
~/.claude/skills/c-jira/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/c-jira/
1Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-jira -a codex2Manually: put the files in place
.agents/skills/c-jira/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-jira -a cursor2Manually: put the files in place
.cursor/skills/c-jira/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install daxaur/openpaw c-jira2Manually: put the files in place
.github/skills/c-jira/SKILL.md1Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-jira -a gemini-cli2Platform CLI
gemini skills install https://github.com/daxaur/openpaw --path skills/c-jiraManually: put the files in place
.devin/skills/c-jira/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add daxaur/openpaw --skill c-jira -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about c-jira
How to install c-jira in Claude Code?
Run npx skills add daxaur/openpaw --skill c-jira -a claude-code in your terminal. The skill file is placed in ~/.claude/skills/c-jira/SKILL.md.
What does c-jira do?
It guides the assistant to manage Jira tickets directly via jira-cli, covering issue creation, transitions, sprint assignments, and comments from the terminal.
What prerequisites are required for c-jira?
You need to install the CLI with brew install ankitpokhrel/jira-cli/jira-cli and run jira init to configure your Jira instance endpoint and authentication tokens.
Source text
SKILL.md · MIT
--- name: c-jira description: Manage Jira issues using `jira` (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser. tags: [jira, issues, project-management, sprints, tickets, atlassian] --- ## What This Skill Does Uses `jira` (jira-cli) to interact with Jira projects — listing issues, creating tickets, moving issues through workflow transitions, and managing sprints. ## CLI Tool: `jira` ### List & View Issues ```bash jira issue list # List issues assigned to you jira issue list --project MYPROJ # Filter by project jira issue list --status "In Progress" # Filter by status jira issue list --type Bug # Filter by issue type jira issue view MYPROJ-123 # View issue details ``` ### Create Issues ```bash jira issue create \ --project MYPROJ \ --type Bug \ --summary "Login page throws 500 error" \ --body "Steps to reproduce: ..." \ --priority High \ --label backend ``` ### Transitions ```bash jira issue move MYPROJ-123 "In Progress" jira issue move MYPROJ-123 "Done" jira issue move MYPROJ-123 "In Review" ``` ### Comments ```bash jira issue comment add MYPROJ-123 --body "Fixed in PR #456" ``` ### Sprints ```bash jira sprint list --project MYPROJ # List sprints jira sprint add MYPROJ-123 --sprint 42 # Add issue to sprint ``` ## Usage Guidelines 1. Always use the full issue key (e.g., `MYPROJ-123`) in commands. 2. Run `jira issue list` before creating tickets to check for existing duplicates. 3. Use `jira issue move` to transition issues — confirm the valid transition names with `jira issue view` first. 4. When the user says "close" or "resolve" an issue, use the appropriate transition name for their workflow. ## Notes - Requires `jira init` to configure server URL and credentials before use. - Install: `brew install ankitpokhrel/jira-cli/jira-cli`
© daxaur · MIT · daxaur/openpaw