Stats
Actions
Tags
From qe-framework
Lightweight Jira CLI wrapper for quick issue management without MCP server setup. Query issues with JQL, create/update tickets, manage sprints, and view boards from the terminal.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qe-framework:Qjira-cliThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
```bash
which jira 2>/dev/null && jira version 2>/dev/null
If NOT installed:
Install: go install github.com/ankitpokhrel/jira-cli/cmd/jira@latest
Or: brew install ankitpokhrel/jira-cli/jira-cli
Based on ankitpokhrel/jira-cli. Manage Jira directly from Bash without an MCP server.
For Confluence, use the
Qatlassian-mcpskill.
jira version # Check installation
jira init # Initial setup (once)
Setup requires: Jira Server URL, login type (api_token), email, API token from id.atlassian.com.
jira issue list -a$(jira me) # My issues
jira issue list -q "project = PROJ AND status = 'In Progress'" # JQL search
jira issue list -p PROJ -s "To Do" -s "In Progress" # By status
jira issue view PROJ-123 # Details
jira issue list -q "project = PROJ" --plain --columns key,summary,status,assignee # Plain output
jira issue create # Interactive
jira issue create -t Bug -p PROJ -s "Login SSO error" -b "Details" -l bug --priority High # One-liner
jira issue create -t Sub-task -p PROJ -s "Add logs" --parent PROJ-123 # Sub-task
jira issue move PROJ-123 "In Progress" # Transition
jira issue edit PROJ-123 -s "Updated title" # Edit fields
jira issue assign PROJ-123 "jane.doe" # Assign
jira issue assign PROJ-123 $(jira me) # Assign to self
jira issue comment add PROJ-123 "Comment text" # Comment
jira issue link PROJ-100 PROJ-101 "Blocks" # Link issues
jira sprint list --current # Current sprint
jira sprint list --prev / --next # Adjacent sprints
jira sprint list --board-id 42 --state active # By board
jira sprint add <sprint-id> PROJ-100 PROJ-101 # Add to sprint
jira board list # All boards
jira board list -t scrum # By type
jira epic list -p PROJ # List epics
jira epic add PROJ-50 PROJ-123 PROJ-124 # Add to epic
jira project list # List projects
# High-priority open bugs
"project = PROJ AND issuetype = Bug AND priority IN (Highest, High) AND resolution IS EMPTY"
# Issues created this week
"project = PROJ AND created >= startOfWeek()"
# Stale issues (14+ days)
"project = PROJ AND updated <= -14d AND resolution IS EMPTY"
# Backlog (no sprint)
"project = PROJ AND sprint IS EMPTY AND resolution IS EMPTY"
# Release blockers
"fixVersion = '2.0' AND priority = Blocker AND resolution IS EMPTY"
jira issue list -p PROJ # Table (default)
jira issue list -p PROJ --plain # Plain text
jira issue list -p PROJ --plain --columns key,summary,status # Select columns
jira issue list -p PROJ --plain --no-headers # No headers
jira issue list -p PROJ --paginate 100 # Page size
echo "=== In Progress ===" && jira issue list -a$(jira me) -s "In Progress" --plain --columns key,summary
echo "=== In Review ===" && jira issue list -a$(jira me) -s "In Review" --plain --columns key,summary
echo "=== Blockers ===" && jira issue list -q "assignee = currentUser() AND status = Blocked" --plain --columns key,summary
| Task | Qjira-cli | Qatlassian-mcp |
|---|---|---|
| Jira issue CRUD / JQL / Sprint | Yes | Yes |
| Confluence / CQL | No | Yes |
| No MCP server required | Yes | No |
| Native Bash piping | Yes | Partial |
MUST DO: Verify jira init complete; store API token securely; watch rate limits; confirm before write ops.
MUST NOT DO: Hardcode tokens; parse output without --plain; use for Confluence (use Qatlassian-mcp).
npx claudepluginhub inho-team/qe-framework --plugin qe-frameworkCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.