risk-assessment

Classify pull requests in the agent-skills repository as LOW, MEDIUM, or HIGH risk.

31|4|Updated Aug 24, 2021
One-click install
npx skills add https://github.com/razorpay/trino-gateway --skill risk-assessment-razorpay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: risk-assessment
Source: https://github.com/razorpay/trino-gateway/tree/main/.agents/skills/risk-assessment
Command: npx skills add https://github.com/razorpay/trino-gateway --skill risk-assessment-razorpay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill defines risk levels (LOW, MEDIUM, HIGH) for PR reviews in the agent-skills repository and provides guidance on when to comment, approve, or request changes, including an auto-approval policy for safe additive changes.

Core Features & Use Cases

  • Defines explicit risk categories and criteria for PR changes.
  • Guides reviewers on actions to take based on detected risk.
  • Includes an auto-approval policy to streamline safe additive changes.

Quick Start

Review a PR by comparing changes to the risk definitions to classify as LOW, MEDIUM, or HIGH and apply the corresponding review actions.

Frequently Asked Questions about risk-assessment

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

FAQPage Schema
How do I classify PR risk levels to guide code review actions?

To classify PR risk, compare changes against defined risk criteria to categorize as LOW, MEDIUM, or HIGH, then apply the corresponding automated validation or human review actions.

What is the auto-approval policy for safe additive changes in PR reviews?

The auto-approval policy streamlines PR reviews by automatically approving safe additive changes classified as LOW risk, reducing manual review overhead for non-destructive modifications.

How do I automate PR validation based on risk categories?

Automated PR validation uses risk classification criteria to map LOW, MEDIUM, and HIGH risk levels to specific reviewer actions, enforcing policies like auto-approval for safe additive changes.

When should I request changes or comment on a pull request based on risk?

Reviewer actions depend on the PR risk classification: LOW risk may trigger auto-approval, while MEDIUM and HIGH risk levels guide reviewers to comment or request changes based on defined criteria.

Can I use risk assessment to enforce code review policies in my repository?

Yes, risk assessment defines explicit risk categories and criteria to enforce code review policies, including auto-approval for safe additive changes and specific actions for MEDIUM or HIGH risk PRs.