Skills Guide

Jira Issue Lookup

VerifiedCaution

Looks up a Jira issue by key and displays its summary, status, assignee, priority, and direct link. Helps quickly fetch key details from Jira without leaving the IDE.

Sby Skills Guide Bot
DevelopmentBeginner
806/2/2026
Claude Code
#jira#issue-lookup#project-management

Recommended for

Backend developerClaude CodeCode reviewFrontend developerFullstack developerRefactoring

Our review

Looks up a Jira issue by its key and displays its details (summary, status, assignee, priority, link).

Strengths

  • Quickly view issue details without leaving the terminal
  • Uses environment variables for secure authentication
  • Retrieves key fields like assignee and priority

Limitations

  • Requires base URL configuration and Jira API tokens
  • Only supports Jira REST API v3
  • No caching or advanced error handling
When to use it

When you need to quickly check the status or details of a Jira issue referenced in a conversation or code.

When not to use it

For complex operations like creating, editing, or advanced searching of Jira issues.

Security analysis

Caution
Quality score85/100

The skill uses bash/curl with environment variables for authentication, performing legitimate Jira API queries. However, the command-line exposure of secrets and dependency on the integrity of the config file introduce moderate risk.

Findings
  • •Credentials passed via command line with curl -u, which may be exposed in process listings or system logs.
  • •Relies on config.yaml for baseUrl; if that config is tampered with, credentials could be sent to an attacker-controlled server.

Examples

Look up a bug ticket
Look up Jira issue PROJ-123
Check a feature status
What's the status of PROJ-456?

name: jira-lookup description: Look up a Jira issue by key. Shows summary, status, assignee, priority, and link. user-invocable: true arguments: "<JIRA-KEY> (e.g. PROJ-123)"

Jira Issue Lookup

Look up a Jira issue using the REST API and display its details.

Steps

  1. Read config.yaml to get features.jira.baseUrl. If not set, ask the user.
  2. Use $JIRA_EMAIL and $JIRA_TOKEN environment variables for authentication.
  3. Fetch the issue via: 
    curl -s -u "$JIRA_EMAIL:$JIRA_TOKEN" \
  -H "Accept: application/json" \
  "${BASE_URL}/rest/api/3/issue/${JIRA_KEY}?fields=summary,status,assignee,priority"
  4. Display the results:
    • Key: PROJ-123
    • Summary: Issue title
    • Status: In Progress
    • Assignee: Name (or Unassigned)
    • Priority: Medium
    • Link: https://company.atlassian.net/browse/PROJ-123

Error Handling

  • If the issue is not found (404), report "Issue not found".
  • If authentication fails (401/403), report "Authentication failed — check JIRA_EMAIL and JIRA_TOKEN env vars".
  • If baseUrl is not configured, report "Jira base URL not configured — set features.jira.baseUrl in config.yaml".
Related skills

Next.js App Router Expert

Development

A skill that turns Claude into a Next.js App Router expert.

Claude CodeCursoradvanced
890
234
2,846
Admin

README Generator

Development

Creates professional and comprehensive README.md files for your projects.

claudeCursorWindsurfbeginner
259
72
821
Admin

API Documentation Writer

Development

Generates comprehensive API documentation in OpenAPI/Swagger format.

claudeCursorWindsurfintermediate
156
44
682
Admin