Skip to content
TrustedSkillsbeta
Back to all skills

Jira:Review

Checked
lobbi-docs·vlatest·productivity·MIT

Analyzes Jira issues to identify potential review gaps, suggest improvements, and ensure thoroughness.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add thelobbi/claude --skill jira:review -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

lobbi-docs

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned lobbi-docs/claude at 1f04f9b061.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1f04f9b061
Manifest
.claude/skills/jira-review/SKILL.md
Scanned
1 file, 28 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill allows AI agents to review Jira issues, providing summaries and identifying potential action items. It can analyze issue descriptions, comments, and associated data to offer concise overviews of the current state of a ticket. The agent can also flag areas needing attention or suggest next steps based on its analysis.

When to use it

  • Quick Issue Understanding: When you need a rapid overview of a Jira issue without reading through lengthy threads.
  • Prioritization Assistance: To quickly assess the urgency and impact of multiple Jira issues for prioritization.
  • Handover Support: When transferring responsibility for an issue, providing a new team member with a summarized understanding.
  • Meeting Preparation: Generate summaries of relevant Jira tickets before a meeting to ensure everyone is on the same page.

Key capabilities

  • Issue Summarization
  • Action Item Identification
  • Jira Data Analysis
  • Concise Reporting

Example prompts

  • "Summarize this Jira ticket: [Ticket ID]"
  • "What are the key action items in issue [Ticket ID]?"
  • "Give me a brief overview of the status of [Ticket ID]."

Tips & gotchas

  • The skill requires access to your Jira instance. Ensure appropriate permissions are configured for the AI agent.