pr-review-integration_skill

This skill helps you validate PRs against Linear requirements by integrating GitHub and Linear MCP to produce actionable reviews.

TypeScript

6

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill lambda-curry/devagent --skill pr-review-integration

SKILL.md4.4 KB

Overview

This skill automates end-to-end PR reviews by tying GitHub pull request data to Linear issue requirements. It validates PR changes against acceptance criteria, identifies gaps, and posts review findings back to both GitHub and Linear. Use it to keep code changes aligned with project requirements and to maintain traceability between code and issues.

How this skill works

The skill extracts PR context using GitHub CLI commands (title, body, changed files, diffs, checks) and parses the PR for Linear issue references. It fetches Linear issue details via the Linear MCP functions to obtain acceptance criteria, labels, comments, and related/dependent issues. The tool compares PR changes to the extracted requirements, evaluates code quality and tests, then generates a structured review that can be posted as a GitHub PR comment and/or a Linear issue comment or update.

When to use it

Validating that a PR implements all acceptance criteria from a Linear issue
Checking for missing requirements or incomplete implementation before merging
Linking code changes to Linear issues for audit and traceability
Posting consolidated review findings to both GitHub PR and the corresponding Linear issue
Assessing dependencies and blocking issues related to the PR

Best practices

Always extract Linear issue IDs from the PR body or branch name as an early step
Validate requirements coverage before performing detailed code-style checks
Include file and line references when documenting gaps to make fixes actionable
Keep a consistent review format so automated comments are easy to scan
Update Linear issue state and comments to reflect review status and next steps
Handle cases with multiple or missing issue links explicitly in the review

Example use cases

A reviewer runs the workflow to confirm a feature branch satisfies all acceptance criteria and posts the summary to the PR and Linear ticket
A release engineer checks that multiple dependent issues referenced in a PR are resolved before approving merge
An automated CI job generates a requirements-coverage report and posts it as a comment on the PR
Product managers receive a Linear comment summarizing missing acceptance items and next steps after code review

FAQ

You need GitHub CLI authenticated for the repo, access to the Linear workspace, and a configured Linear MCP endpoint or client.

How does the skill find which Linear issue a PR targets?

It scans the PR body (and optionally branch names) for Linear issue IDs, then uses those IDs to fetch issue details and acceptance criteria.