From meain-dotfiles
Manages Jira issues via jira CLI: view details, list/search with filters/JQL, create, edit fields, transition status, assign, comment, link. Triggers on /jira, issue keys like PROJ-123, or phrases like 'check ticket'.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-2 --plugin meain-dotfilesUse the `jira` CLI to look up, create, edit, transition, assign, comment on, and link Jira issues. - The user mentions a Jira issue key (e.g., `DP-123`) - The user asks to look up, check, or get details on a Jira ticket - The user wants to list or search for issues in a project - The user wants to create, edit, transition, assign, comment on, or link issues - The user needs context from a Jira ...
Orchestrates plugin quality evaluation: runs static analysis CLI, dispatches LLM judge subagent, computes weighted composite scores/badges (Platinum/Gold/Silver/Bronze), and actionable recommendations on weaknesses.
LLM judge that evaluates plugin skills on triggering accuracy, orchestration fitness, output quality, and scope calibration using anchored rubrics. Restricted to read-only file tools.
Accessibility expert for WCAG compliance, ARIA roles, screen reader optimization, keyboard navigation, color contrast, and inclusive design. Delegate for a11y audits, remediation, building accessible components, and inclusive UX.
Use the jira CLI to look up, create, edit, transition, assign, comment on, and link Jira issues.
DP-123)Determine which operation the user needs:
| Intent | Operation |
|---|---|
| View issue details | view |
| Search/list issues | list |
| Create a new issue | create |
| Edit fields on an issue | edit |
| Change issue status | move |
| Assign/unassign an issue | assign |
| Add a comment | comment |
| Link two issues | link |
| Open in browser | open |
jira issue view ISSUE-KEY --plain
To include recent comments:
jira issue view ISSUE-KEY --plain --comments 5
To get full raw JSON data for deeper inspection:
jira issue view ISSUE-KEY --raw
# List issues in the default project
jira issue list --plain --no-truncate
# Filter by status
jira issue list --plain -s "In Progress"
# Filter by assignee (use "me" for current user)
jira issue list --plain -a "user@example.com"
# Filter by type and status
jira issue list --plain -t Bug -s "To Do"
# Filter by priority
jira issue list --plain -y High
# Filter by label
jira issue list --plain -l backend
# Search by text
jira issue list "search query" --plain
# Combine filters
jira issue list --plain -s "In Progress" -a "me" -y High
# Use raw JQL for complex queries
jira issue list --plain -q "assignee = currentUser() AND status = 'In Progress'"
# Specify a different project
jira issue list --plain -p PROJECT_KEY
# Limit results
jira issue list --plain --paginate 20
Always use --no-input to avoid interactive prompts.
# Basic creation
jira issue create -tTask -s "Summary here" -b "Description here" --no-input
# With priority, labels, assignee
jira issue create -tBug -s "Bug title" -yHigh -lbug -lurgent -a "user@example.com" -b "Bug description" --no-input
# Create subtask under a parent
jira issue create -tSubtask -P PARENT-KEY -s "Subtask title" -b "Details" --no-input
# In a specific project
jira issue create -p PROJECT -tStory -s "Story title" -b "As a user..." --no-input
# With custom fields
jira issue create -tStory -s "Story" --custom story-points=3 --no-input
# Pipe description from stdin for long bodies
echo "Long description here" | jira issue create -tTask -s "Summary" --no-input
Issue types: Task, Bug, Story, Epic, Subtask
Always use --no-input to avoid interactive prompts.
# Edit summary
jira issue edit ISSUE-KEY -s "New summary" --no-input
# Edit description
jira issue edit ISSUE-KEY -b "New description" --no-input
# Change priority
jira issue edit ISSUE-KEY -y High --no-input
# Add labels (append)
jira issue edit ISSUE-KEY -l newlabel --no-input
# Remove a label (prefix with -)
jira issue edit ISSUE-KEY --label -oldlabel --no-input
# Change assignee
jira issue edit ISSUE-KEY -a "user@example.com" --no-input
# Edit custom fields
jira issue edit ISSUE-KEY --custom story-points=5 --no-input
# Combine multiple edits
jira issue edit ISSUE-KEY -s "Updated title" -yHigh -l backend --no-input
# Move issue to a new status
jira issue move ISSUE-KEY "In Progress"
jira issue move ISSUE-KEY "Done"
# Move with a comment
jira issue move ISSUE-KEY "Done" --comment "Completed in PR #123"
# Move and reassign
jira issue move ISSUE-KEY "In Review" -a "reviewer@example.com"
# Assign to a user
jira issue assign ISSUE-KEY "user@example.com"
# Assign to self
jira issue assign ISSUE-KEY $(jira me)
# Unassign
jira issue assign ISSUE-KEY x
Always use --no-input to avoid interactive prompts.
# Add a comment
jira issue comment add ISSUE-KEY --no-input "Comment text here"
# Multi-line comment
jira issue comment add ISSUE-KEY --no-input $'First line\n\nSecond paragraph'
# Internal comment (not visible to external users)
jira issue comment add ISSUE-KEY --no-input "Internal note" --internal
# Link two issues
jira issue link ISSUE-1 ISSUE-2 "Blocks"
jira issue link ISSUE-1 ISSUE-2 "Duplicate"
# Unlink
jira issue unlink ISSUE-1 ISSUE-2
# List sprints
jira sprint list --plain
# Add issues to a sprint
jira sprint add SPRINT_ID ISSUE-KEY
# Add issues to an epic
jira epic add EPIC-KEY ISSUE-KEY
# Remove from epic
jira epic remove ISSUE-KEY
jira open ISSUE-KEY
For read operations, summarize clearly:
For write operations, confirm what was done:
When the user needs issue context for coding work, focus on:
--plain flag when listing/viewing issues so output is parseable (avoid the interactive TUI)--no-input flag on create/edit/comment to avoid interactive prompts--no-truncate with list commands to show full field contents when details matterjira initDP (Data Pipelines) — only specify -p when targeting a different project