find-jira-task

Find a Jira ticket key from branch names, commits, and PR metadata.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fyodoriv/agentbrew --skill find-jira-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: find-jira-task
Source: https://github.com/fyodoriv/agentbrew/tree/main/skill-plugins/dev/find-jira-task
Command: npx skills add https://github.com/fyodoriv/agentbrew --skill find-jira-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira ticket selection for commits and PRs can be time-consuming and error-prone; this skill automates finding the most relevant ticket to append to messages, reducing context switching.

Core Features & Use Cases

  • Branch-based ticket extraction: derive a ticket key from the current branch pattern.
  • Commit/PR context analysis: inspect recent commits and PR titles to surface the correct Jira key.
  • Safe fallback: gracefully return no ticket when confidence is insufficient, avoiding mislabeling.
  • Use Case: When preparing a commit, this skill suggests the appropriate Jira ticket to decorate the message.

Quick Start

Ask the agent to return the Jira ticket key for the current branch or pull request to append to your commit or PR title.

Frequently Asked Questions about find-jira-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically find the Jira ticket key for my current git branch and commit?

To find the Jira ticket key for a git branch and commit, the skill scans branch names, recent commits, and PR metadata to locate a confident match and returns that key for your commit message.

Can I extract a Jira ticket number from a pull request title using the GitHub CLI?

Yes, you can extract a Jira ticket number from PR metadata using the GitHub CLI. The skill analyzes PR titles alongside recent git commits to identify and return the correct Jira key.

What happens when the Jira ticket extraction confidence is insufficient for a commit?

When Jira ticket extraction confidence is insufficient for a commit, the skill safely returns no ticket. This graceful fallback prevents mislabeling your commit or PR title with an incorrect key.

Do I need Jira API access to map branch names to Jira ticket keys?

No, you do not need Jira API access to map branch names to Jira ticket keys. The skill requires git, the GitHub CLI, and Jira context, but it does not read ticket details or create new tickets.

What is the best way to automate appending Jira ticket numbers to pull request titles?

The best way to automate appending Jira ticket numbers to PR titles is by analyzing branch patterns and recent commit context. The skill derives the correct key and safely stops upon finding a confident match.