jira-integration-ai-kit

Extract Jira issue context from branch names and pull requests.

Updated May 11, 2026
One-click install
npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill jira-integration-ai-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-integration-ai-kit
Source: https://github.com/ducthang-hub/nw-ai-kit/tree/main/.agents/skills/jira-integration-ai-kit
Command: npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill jira-integration-ai-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork in development tasks by helping you reliably extract and apply Jira issue context (requirements, acceptance criteria, and related details) when working from branches and pull requests.

Core Features & Use Cases

  • Branch-to-Jira Context Extraction: Extracts issue numbers from branch patterns like feature/ITDEV-12345 to determine which Jira ticket to use.
  • Jira Issue Lookup & Understanding: Fetches Jira issue details via mcp_atlassian_getJiraIssue or searches with mcp_atlassian_searchJiraIssuesUsingJql to understand the full ticket context.
  • Implementation Guidance With Ticket Requirements: Applies the ticket’s description, comments, labels, linked PRs, and custom fields to guide implementation and review.
  • PR Linking Support: Uses Jira context to help connect pull requests to the correct Jira issues.

Quick Start

Ask your AI to read the Jira ticket referenced by your branch name ITDEV-12345 and summarize the requirements and acceptance criteria you should follow before writing or reviewing code.

Frequently Asked Questions about jira-integration-ai-kit

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

FAQPage Schema
How do I link a Jira issue to a pull request using a branch name?

To link a Jira issue to a pull request, this Skill parses branch patterns like feature/ITDEV-12345 to extract the ticket ID and fetches the corresponding issue context. It translates the ticket description and custom fields into actionable development requirements for your PR.

How do I get Jira ticket requirements before writing code?

You can get Jira ticket requirements before writing code by searching issues with JQL or retrieving them directly. The Skill extracts the description, comments, and labels to provide implementation guidance and prevent requirement drift during development.

Can I use JQL to search Jira issues for code review context?

Yes, you can use JQL to search Jira issues for code review context. The Skill uses mcp_atlassian_searchJiraIssuesUsingJql to find relevant tickets, then translates issue details and linked PRs into actionable review criteria.

What Jira issue details are extracted for implementation guidance?

Extracted Jira issue details for implementation guidance include the ticket description, comments, labels, linked PRs, and custom fields. The Skill retrieves this context via mcp_atlassian_getJiraIssue to align your development work with acceptance criteria.

Does this Skill require mcp-atlassian to read Jira issues?

Yes, reading Jira issues requires the mcp-atlassian integration. The Skill specifically depends on mcp_atlassian_getJiraIssue and mcp_atlassian_searchJiraIssuesUsingJql to fetch ticket details and support branch-to-Jira context extraction.

Why does my branch name need to match a Jira issue number format?

Your branch name needs to match a Jira issue number format like ITDEV-12345 so the parser can reliably identify the correct ticket. Extracting this context from the branch prevents requirement drift and wasted review cycles by ensuring accurate PR-to-ticket linking.