assess-pr-risk

Assess pull request risk across seven dimensions and optionally post the assessment as a GitHub comment.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill assess-pr-risk-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: assess-pr-risk
Source: https://github.com/pnewsam/skills/tree/main/archive/assess-pr-risk
Command: npx skills add https://github.com/pnewsam/skills --skill assess-pr-risk-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewers often lack a structured way to judge whether a pull request is safe to merge, especially for large diffs touching security, data, or infrastructure. This Skill produces a consistent, evidence-based risk rating for any PR. ## Core Features & Use Cases - Seven-dimension risk model: Rates blast radius, change type, security sensitivity, data risk, test coverage, dependencies, and infrastructure/config on a Low-to-Critical scale. - Analyze and Post modes: Runs read-only analysis by default and posts a formatted comment to the PR only when explicitly requested. - Flexible GitHub access: Works through an authenticated GitHub connector or the gh CLI, with safe handling of merged PRs and very large diffs. - Use Case: Before merging a PR that modifies authentication logic and drops a database column, run the assessment to get a Critical rating with traceable findings and concrete recommendations for the author. ## Quick Start Use the assess-pr-risk skill to evaluate the risk of PR #142 without posting a comment.

Frequently Asked Questions about assess-pr-risk

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

FAQPage Schema
How do I assess the risk of a GitHub pull request before merging?▼

Run the assessment against the PR number or current branch; it fetches the diff and metadata via a GitHub connector or gh CLI, then rates seven risk dimensions from Low to Critical with findings traceable to specific files.

What risk factors does a PR risk assessment check?▼

It evaluates blast radius, change type, security sensitivity, data risk, test coverage, dependency changes, and infrastructure or configuration changes. The overall level is the highest credible single-dimension rating, calibrated with evidence.

Does the risk assessment post a comment on the pull request automatically?▼

No. Analyze mode is the default and produces no external writes. A comment is posted only in Post mode, when the user explicitly asks to publish the assessment to the PR.

Can I assess PR risk without the gh CLI installed?▼

Yes. The skill prefers an available authenticated GitHub connector or app and falls back to authenticated gh. If neither path is authenticated, it stops and explains how to connect one.

How are very large pull requests with 500+ files handled?▼

The assessment samples representative files from each affected module using PR file metadata instead of reading every file. The comment notes the sampling and flags the diff size itself as a High blast-radius indicator.