jira-pr-verify

To verify a GitHub PR against Jira acceptance criteria, provide a Jira issue key and PR URL. The skill inspects PR diffs and CI signals to map each Jira goal to concrete evidence, generating a traceability ledger with an overall PASS, PARTIAL, FAIL, or BLOCKED verdict.

You can automate Jira to PR traceability by supplying a Jira issue key and PR URL. The verification process loads trusted Jira artifacts, inspects PR details, and posts an actionable PR comment draft mapping each Jira requirement to specific code changes and test evidence.

A Jira PR verification traceability ledger is a mapping of Jira goals, requirements, and acceptance criteria to concrete PR evidence. It provides per-item verdicts like met, partially_met, not_met, or unverifiable, alongside artifact paths and evidence pointers for review.

Jira PR verification works without external dependencies. It uses provided Jira issue keys and PR URLs to fetch context, inspect CI status, and analyze diffs to evaluate implementation coverage and generate a ready-to-post PR comment with evidence pointers.

To audit implementation coverage for a Jira story in a pull request, provide the Jira issue key and PR URL. The skill matches Jira requirements to PR changes and CI signals, producing a coverage summary with per-item verdicts and an overall PASS, PARTIAL, FAIL, or BLOCKED verdict.

When verifying partially met Jira goals in a PR, limitations arise if CI signals are incomplete or Jira artifacts lack detailed acceptance criteria. The skill may return a PARTIAL verdict or mark items as unverifiable if concrete evidence cannot be mapped from the PR diff.