jira-lookup — community jira-lookup, claude-code-reviewer, community, ide skills

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing efficient Jira issue tracking and management using REST API Look up a Jira issue by key. Shows summary, status, assignee, priority, and link.

martin-janci martin-janci
[0]
[1]
Updated: 2/13/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
33
Canonical Locale
en
Detected Body Locale
en

Perfect for Development Agents needing efficient Jira issue tracking and management using REST API Look up a Jira issue by key. Shows summary, status, assignee, priority, and link.

Core Value

Empowers agents to automate Jira issue lookup using the REST API, providing efficient issue tracking and management with features like authentication via environment variables $JIRA_EMAIL and $JIRA_TOKEN, and fetching issue details in JSON format

Ideal Agent Persona

Perfect for Development Agents needing efficient Jira issue tracking and management using REST API

↓ Capabilities Granted for jira-lookup

Automating Jira issue tracking and management
Fetching issue details via REST API for efficient project monitoring
Displaying issue status, assignee, and priority for streamlined team collaboration

! Prerequisites & Limits

  • Requires Jira REST API access
  • Needs $JIRA_EMAIL and $JIRA_TOKEN environment variables for authentication
  • Dependent on config.yaml for features.jira.baseUrl

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team handoff, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is jira-lookup?

Perfect for Development Agents needing efficient Jira issue tracking and management using REST API Look up a Jira issue by key. Shows summary, status, assignee, priority, and link.

How do I install jira-lookup?

Run the command: npx killer-skills add martin-janci/claude-code-reviewer/jira-lookup. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for jira-lookup?

Key use cases include: Automating Jira issue tracking and management, Fetching issue details via REST API for efficient project monitoring, Displaying issue status, assignee, and priority for streamlined team collaboration.

Which IDEs are compatible with jira-lookup?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for jira-lookup?

Requires Jira REST API access. Needs $JIRA_EMAIL and $JIRA_TOKEN environment variables for authentication. Dependent on config.yaml for features.jira.baseUrl.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add martin-janci/claude-code-reviewer/jira-lookup. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use jira-lookup immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

jira-lookup

Install jira-lookup, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

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: 
    bash
    1curl -s -u "$JIRA_EMAIL:$JIRA_TOKEN" \
2  -H "Accept: application/json" \
3  "${BASE_URL}/rest/api/3/issue/${JIRA_KEY}?fields=summary,status,assignee,priority"
  4. Display the results:

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

Looking for an alternative to jira-lookup or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

The React Framework

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

★ 98.6k
⑂ 0
Developer