pr-jira-audit

Audits merge/pull requests for missing Jira issue references and optionally creates issues and adds comments.

2|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/dmzoneill/skills --skill pr-jira-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-jira-audit
Source: https://github.com/dmzoneill/skills/tree/main/pr-jira-audit
Command: npx skills add https://github.com/dmzoneill/skills --skill pr-jira-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that all Merge Requests (MRs) and Pull Requests (PRs) have a corresponding Jira issue linked, improving traceability and project management hygiene.

Core Features & Use Cases

  • Scan Open MRs/PRs: Automatically checks the titles and descriptions of open merge requests for valid Jira issue keys (e.g., [A-Z]{2,10}-\d+).
  • Compliance Reporting: Provides a clear summary of which MRs/PRs are compliant and which are missing Jira references.
  • Optional Jira Issue Creation: Can automatically create a new Jira issue for MRs/PRs that lack a Jira link, streamlining the process of linking work.
  • Use Case: When preparing for a sprint review, use this skill to quickly identify any code changes that haven't been properly linked to their corresponding tasks or bugs in Jira.

Quick Start

Audit open merge requests for Jira links in the current project and report compliance.

Frequently Asked Questions about pr-jira-audit

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

FAQPage Schema
How do I check merge requests for missing Jira links?

To check merge requests for missing Jira links, scan open MRs and PRs to audit titles, descriptions, and commits for valid Jira issue references. It provides a compliance report showing which code changes lack proper task traceability.

How does PR compliance auditing work for Jira issue references?

PR compliance auditing works by scanning merge request titles and descriptions for valid Jira issue keys using a specific pattern. It identifies unlinked code changes and optionally creates Jira issues for them, adding comments with the generated issue key.

Can I automatically create Jira issues for unlinked pull requests?

Yes, you can automatically create Jira issues for unlinked pull requests. The audit process identifies MRs missing a Jira reference, creates a corresponding issue, and adds a comment to the MR with the newly generated issue key.

Does this Jira link audit support GitLab merge requests?

Yes, this Jira link audit supports GitLab merge requests. It scans open MRs on GitLab, checking titles and descriptions for valid Jira issue keys, and has potential compatibility with other Git platforms.

What is the best way to ensure all pull requests have a Jira issue linked?

The best way to ensure pull requests have a Jira issue linked is to run an audit that scans open MRs for valid issue keys. It flags non-compliant code changes and can optionally generate missing Jira issues automatically.