.config/opencode/skills/jira-ticket-fetcher/SKILL.md
This skill should be used when users need to fetch Jira ticket content using either a specific ticket ID (like RD-3891) or search for tickets by title/description. It defaults to searching within the current sprint but can extend to all tickets when needed. The skill uses the Jira CLI to retrieve ticket details, status, assignee, and descriptions.
npx skillsauth add alexismanuel/dotfiles jira-ticket-fetcherInstall 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.
This skill enables fetching Jira ticket content using the Jira CLI. It supports retrieving specific tickets by ID or searching for tickets by text content, with configurable search scope (current sprint vs all projects).
To fetch a Jira ticket, determine the input type:
Before using this skill, ensure the following are installed:
curl -LsSf https://astral.sh/uv/install.sh | sh or brew install uvbrew install jira-cligo install github.com/ankitpokhrel/jira-cli/cmd/jira@latestThe Jira CLI requires authentication before use:
Generate an API token:
Set up authentication (choose one method):
export JIRA_API_TOKEN=your_token.netrc file with machine detailsjira initTest authentication: jira me
For detailed setup instructions: https://github.com/ankitpokhrel/jira-cli#getting-started
Use when the user provides a specific ticket identifier:
# Primary (recommended)
uv run scripts/fetch_ticket.py RD-3891
# Alternative (if uv not available)
python scripts/fetch_ticket.py RD-3891
The script automatically detects ticket ID patterns (PROJECT-NUMBER format) and retrieves full ticket details including:
Use when the user provides descriptive text or vague ticket references:
# Search in current sprint (default)
uv run scripts/fetch_ticket.py "engine i18n epic"
# Search across all projects
uv run scripts/fetch_ticket.py "engine i18n epic" all
# Alternative (if uv not available)
python scripts/fetch_ticket.py "engine i18n epic"
python scripts/fetch_ticket.py "engine i18n epic" all
Search functionality includes:
Is the input a ticket ID? (Pattern: PROJECT-NUMBER)
get_ticket_by_id() functionIs the user looking for current sprint tickets only?
search_tickets_by_text() with scope='current'search_tickets_by_text() with scope='all'Handle errors gracefully
The scripts/fetch_ticket.py provides these key functions:
get_ticket_by_id(ticket_id): Retrieves specific ticket detailssearch_tickets_by_text(search_text, scope): Searches tickets by contentget_current_sprint_tickets(): Gets all current sprint ticketsis_ticket_id(input_text): Validates ticket ID format# Primary (recommended)
uv run scripts/fetch_ticket.py <ticket_id_or_search_text> [scope]
# Alternative (if uv not available)
python scripts/fetch_ticket.py <ticket_id_or_search_text> [scope]
<ticket_id_or_search_text>: Either a ticket ID (e.g., RD-3891) or search text[scope]: Optional. Either current (default) or allThe script includes comprehensive error handling for:
Results are formatted for readability with:
fetch_ticket.py: Main Python script for Jira ticket operations
jira_cli_commands.md: Comprehensive Jira CLI command reference
User: "Show me ticket RD-3891"
→ Execute: uv run scripts/fetch_ticket.py RD-3891
→ Returns: Full ticket details with status, assignee, description
User: "Find the engine i18n epic"
→ Execute: uv run scripts/fetch_ticket.py "engine i18n epic"
→ Returns: Matching tickets from current sprint
User: "Search for all tickets about authentication"
→ Execute: uv run scripts/fetch_ticket.py "authentication" all
→ Returns: Matching tickets from all projects
development
Generate GitLab merge request descriptions from git commits with automatic categorization and Jira integration.
development
This skill should be used when validating that an implementation plan was correctly executed. It verifies success criteria, runs tests, identifies deviations, and presents structured completion options including MR creation or discard.
development
This skill should be used when reviewing code changes in a branch against main/master/develop. It analyzes commits, integrates JIRA ticket and MR context when available, and produces a structured code review using Conventional Comments format.
development
This skill should be used when conducting comprehensive codebase research to answer questions, understand architecture, or prepare context for implementation planning. It spawns parallel sub-agents and synthesizes findings into a structured research document.