skills.rest
flurdy
flurdyCOMMUNITY
Explore all skills by this author →
Website𝕏@flurdyGitHub

review-pr

Compare GitHub PR changes and CI status against linked Jira ticket requirements.

6|Updated Jan 22, 2026
Search Tags:#github#review#jira#code-review#ci#pull-request
One-click install
npx skills add https://github.com/flurdy/agent-skills --skill review-pr-flurdy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/flurdy/agent-skills/tree/main/skills/review-pr
Command: npx skills add https://github.com/flurdy/agent-skills --skill review-pr-flurdy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually validating that PR changes satisfy Jira ticket requirements is error-prone and time-consuming. This skill automates the validation by comparing code changes, PR metadata, and CI status to the linked Jira ticket, producing an acceptance criteria checklist and a concise risk report.

Core Features & Use Cases

  • Automated PR metadata retrieval: fetches PR title, body, additions, deletions, files changed, and author information from GitHub (gh CLI) to inform the review.
  • Jira ticket alignment: extracts and loads Jira ticket details to compare against PR changes and acceptance criteria.
  • AC checklist generation: constructs a structured acceptance criteria checklist highlighting pass/fail gaps and notable concerns.
  • CI status awareness: includes CI results from GH checks to assess integration readiness.
  • Use Case: For a sprint, automatically review a PR against its Jira ticket to ensure scope and acceptance criteria are met before merge.

Quick Start

Provide a PR number to initiate the review and receive a structured AC checklist and summary.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate GitHub pull request reviews against Jira ticket requirements?▼

Automating PR reviews against Jira requirements involves fetching PR metadata and CI status via GitHub CLI, extracting Jira ticket acceptance criteria, and generating a pass/fail checklist. This skill compares code changes to Jira tickets to produce an automated risk report.

Can I use GitHub CLI and Jira together to validate acceptance criteria before merging?▼

Yes, validating acceptance criteria before merging uses GitHub CLI to retrieve PR details and Jira MCP to load ticket data. This skill cross-references PR descriptions and CI checks against Jira requirements to output an actionable summary of identified concerns.

What is the best way to generate an acceptance criteria checklist for a pull request?▼

Generating an acceptance criteria checklist for a pull request requires linking code changes to Jira ticket details. This skill automatically constructs a structured checklist highlighting pass/fail gaps and notable concerns by comparing code diffs, PR metadata, and CI status.

Does this automated code review process include CI status checks from GitHub?▼

Yes, the automated code review process includes CI status checks from GitHub. This skill fetches GitHub check results to assess integration readiness and incorporates CI outcomes into the final review summary alongside Jira requirement alignment.

How do I start an automated PR review if I only have a PR number?▼

Starting an automated PR review with a PR number triggers the workflow to fetch metadata from GitHub and linked Jira details. You receive a structured acceptance criteria checklist and a concise risk report summarizing validation gaps.

What are the limitations of automating Jira requirement validation for code changes?▼

Automating Jira requirement validation for code changes is limited to GitHub-based PRs and requires linked Jira tickets to function. This skill relies on GitHub CLI and Jira MCP data, meaning unlinked PRs or unsupported platforms will not produce an acceptance criteria checklist.

Related Skills

Explore More Software Engineering Skills→
derrybirkettderrybirkett
1

work-monitor

Aggregate GitHub pull request and Jira ticket updates for work visibility.

Community
Intermediate
markus41markus41
18

jira:review

Review linked commits and pull requests for a Jira issue against acceptance criteria.

Community
Intermediate
bketelsenbketelsen
1

remediate-failures

Correct QA review failures and rule violations until quality gates pass.

Community
Advanced
esassocesassoc
6

precommit-review

Analyze uncommitted code diffs for bugs, security issues, and standards.

Official
Advanced