gemini/skills/jira/SKILL.md
Use jira CLI for Jira operations including issue management, project queries, transitions, and JQL search
npx skillsauth add lanej/dotfiles jiraInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are a Jira specialist using the jira CLI tool. This skill provides comprehensive guidance for working with Jira through a custom CLI.
# Check authentication status
jira auth check
# Login to Jira
jira auth login
# View issue details
jira issue get ISSUE-123
# Create new issue
jira issue create --project PROJ --type Bug --summary "Issue summary" --description "Description"
# Update issue
jira issue update ISSUE-123 --summary "New summary"
# Add comment to issue
jira comment add ISSUE-123 "Comment text"
# List comments on issue
jira comment list ISSUE-123
# List available transitions for an issue
jira transition list ISSUE-123
# Transition issue to new status
jira transition ISSUE-123 "In Progress"
# Search issues with JQL
jira search "project = PROJ AND status = Open"
# Search with output format
jira search "assignee = currentUser()" --format json
# Search with field selection
jira search "project = PROJ" --fields summary,status,assignee
# List all projects
jira project list
# Get project details
jira project get PROJ
# Watch an issue
jira watch add ISSUE-123
# Stop watching an issue
jira watch remove ISSUE-123
# Assign issue
jira assign ISSUE-123 username
# Assign to self
jira assign ISSUE-123 me
# View issues assigned to you
jira search "assignee = currentUser() AND status != Done"
# View issues you're watching
jira search "watcher = currentUser()"
# View recent activity
jira search "updatedDate >= -7d AND assignee = currentUser()"
# Create a bug
jira issue create --project PROJ --type Bug \
--summary "Login button not working" \
--description "Steps to reproduce..."
# Update priority
jira issue update ISSUE-123 --priority High
# Add labels
jira issue update ISSUE-123 --labels bug,frontend
# Link issues
jira link add ISSUE-123 ISSUE-456 "blocks"
# Start work on issue
jira transition ISSUE-123 "In Progress"
# Mark as done
jira transition ISSUE-123 "Done"
# Reopen issue
jira transition ISSUE-123 "Reopen"
# Issues in specific project
jira search "project = MYPROJ"
# Open issues assigned to you
jira search "assignee = currentUser() AND status in (Open, 'In Progress')"
# High priority bugs
jira search "type = Bug AND priority = High"
# Recently updated issues
jira search "updated >= -1w"
# Issues created this sprint
jira search "sprint in openSprints() AND created >= startOfWeek()"
# Issues with specific label
jira search "labels = urgent"
# Issues in epic
jira search "'Epic Link' = EPIC-123"
project - Project key or namestatus - Issue status (Open, In Progress, Done, etc.)assignee - Assigned user (use currentUser() for yourself)reporter - Issue reporterpriority - Priority level (Highest, High, Medium, Low, Lowest)type - Issue type (Bug, Story, Task, Epic, etc.)labels - Issue labelscreated - Creation dateupdated - Last update dateresolution - Resolution statuscurrentUser() - Current logged-in userstartOfDay(), startOfWeek(), startOfMonth() - Date functionsnow() - Current timestampopenSprints() - Currently active sprintsclosedSprints() - Completed sprints# JSON output (for scripting)
jira search "project = PROJ" --format json
# Table output (human-readable, default)
jira search "project = PROJ" --format table
# CSV output
jira search "project = PROJ" --format csv
jira auth check before operations--format json for scripting--fields to limit returned datajira transition list before transitioning# What you worked on yesterday
jira search "assignee = currentUser() AND updated >= -1d"
# What you're working on today
jira search "assignee = currentUser() AND status = 'In Progress'"
# Unassigned bugs
jira search "type = Bug AND assignee is EMPTY AND status = Open"
# Critical bugs in project
jira search "project = PROJ AND type = Bug AND priority in (Highest, High)"
# Issues in backlog
jira search "project = PROJ AND status = 'To Do' AND sprint is EMPTY"
# Issues in current sprint
jira search "project = PROJ AND sprint in openSprints()"
# Completed this sprint
jira search "project = PROJ AND sprint in openSprints() AND status = Done"
If you encounter authentication errors:
jira auth login
If JQL syntax errors occur:
AND, OR, NOT operators (uppercase)# View issue
jira issue get ISSUE-123
# Search
jira search "JQL query here"
# Create
jira issue create --project PROJ --type TYPE --summary "text"
# Update
jira issue update ISSUE-123 --field value
# Transition
jira transition ISSUE-123 "Status Name"
# Comment
jira comment add ISSUE-123 "Comment text"
# Assign
jira assign ISSUE-123 username
devops
DORA engineering metrics project at ~/src/dora. Load when: querying DORA BigQuery views (deployment frequency, lead time, change failure rate, alerts, review time) from any project; joining against DORA.unified_identity or DORA_clean.* views from any project; running the data pipeline (just refresh, just download-*, just upload-*); making OpenTofu infrastructure changes to DORA tables or views; working with team attribution, team identity, or engineer roster data.
development
Data pipeline architecture patterns and best practices, including medallion/three-layer architecture (Raw/Staging/Enriched or Bronze/Silver/Gold), YAML-based schema management, and ETL workflow patterns. Use when designing or implementing data pipelines, working with data warehouse layers, or managing table schemas in YAML.
data-ai
Delegate research and context-gathering tasks to a sub-agent to protect the primary context window. Use when the user asks to "research X", "look into X", "find out about X", "gather context on X", or any investigative framing where answering requires 2+ searches or multiple sources. Also use proactively before starting substantive work when prior context is unknown. Never run research inline — always delegate.
documentation
--- name: qmd-math description: Math notation conventions for Quarto/EPQ documents rendered via lualatex. Use when: writing or adding a formula, equation, or mathematical expression to a .qmd file; asked about display math, inline math, or LaTeX notation in a QMD/Quarto context; defining a where-clause or variable definitions for an equation; converting prose variable descriptions into structured math notation; fixing math that renders badly in a PDF; using \lvert, \begin{aligned}, \tfrac, \text