skills.rest
Burburton
BurburtonCOMMUNITY
Explore all skills by this author →
GitHub

risk-review

Identify and document technical risks for software changes.

Updated Mar 22, 2026
Search Tags:#monitoring#rollback#risk-analysis#independent-verification#risk-report#risk-review
One-click install
npx skills add https://github.com/Burburton/amazing_agent_specialist --skill risk-review-burburton
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: risk-review
Source: https://github.com/Burburton/amazing_agent_specialist/tree/main/.opencode/skills/reviewer/risk-review
Command: npx skills add https://github.com/Burburton/amazing_agent_specialist --skill risk-review-burburton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Risk-review provides a structured framework to identify, assess, and document technical risks that accompany software changes, ensuring independent verification and compliant reporting.

Core Features & Use Cases

  • Structured risk taxonomy aligned with BR-002, BR-004, BR-007 for consistent reviews.
  • Guides through high-risk area identification, failure scenario analysis, rollback assessment, monitoring gaps, and fault tolerance review.
  • Produces a standardized risk_review_report artifact for downstream teams (developers, security, operations).

Quick Start

Run the risk-review on a change package to generate a BR-compliant risk assessment report.

Frequently Asked Questions about risk-review

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

FAQPage Schema
How do I assess technical risks for software changes before deployment?▼

Risk-review systematically identifies and documents technical risks for software changes across codebases, services, and integrations, ensuring independence validation and producing a structured risk_review_report artifact.

What is included in a software risk analysis for data migrations and new features?▼

A software risk analysis covers high-risk area identification, failure scenario analysis, rollback assessment, monitoring gaps, and fault tolerance review, aligning with BR-002, BR-004, and BR-007 compliance requirements.

How do I document rollback assessment and monitoring gaps for architectural changes?▼

You document rollback assessment and monitoring gaps by applying a structured risk taxonomy that evaluates failure scenarios and fault tolerance, outputting a compliant risk_review_report for downstream teams.

Can I generate a standardized risk report for developers, security, and operations teams?▼

Yes, you can generate a standardized risk_review_report artifact that provides downstream teams including developers, security, and operations with a compliant and structured technical risk assessment.

How does independent verification work during a technical risk review?▼

Independent verification works by applying BR-002 independence validation during the risk assessment process, ensuring that technical risks for architectural changes and deployments are evaluated objectively and disclosed comprehensively.

Related Skills

Explore More Software Engineering Skills→
maosanhioromaosanhioro

implementation-safety

Enforce minimal diffs with tests and documentation updates for software changes.

Community
Intermediate
ikeisukeikeisuke
24

reviewing-operations-deploy

Review deployment plans for completeness, rollback procedures, and monitoring configurations.

Community
Intermediate
pacphipacphi
14

import-to-ontology

Migrate Markdown blocks into ontology files with OWL2 validation and rollback on failure.

Community
Advanced
ckrono-progckrono-prog

security_scan

Conducts a multi-scanner security audit of a codebase for critical and high vulnerabilities.

Community
Intermediate