skills.rest
cryborg1211
cryborg1211COMMUNITY
Explore all skills by this author →
GitHub

Review Changes

Analyze code changes and impacts to produce risk-level grouped review reports.

Updated May 10, 2026
Search Tags:#automation#quality-assurance#code-review#test-coverage#risk-analysis#impact-analysis#change-detection
One-click install
npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill review-changes-cryborg1211
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Review Changes
Source: https://github.com/cryborg1211/quant_trading_telegram_bot/tree/main/.vibecode-backup/.claude/skills/review-changes
Command: npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill review-changes-cryborg1211

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perform a structured, risk-aware code review by detecting changes and assessing their impact across the codebase.

Core Features & Use Cases

  • Change detection: Identify modified functions and data flows.
  • Impact analysis: Map changes to affected execution paths using a knowledge graph for context.
  • Guided testing: Recommend targeted tests for high-risk changes and verify coverage in test suites.

Quick Start

Run detect_changes to initialize the risk-scoped review on the latest commit.

Frequently Asked Questions about Review Changes

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

FAQPage Schema
How do I automate code review with risk and impact analysis?▼

Automate risk-aware code review by detecting changes and mapping their impacts across affected execution paths. This process groups findings by risk level, detailing coverage status and recommended fixes.

What is the best way to map code changes to affected execution paths?▼

Mapping code changes to affected paths uses a knowledge graph to assess impact across components. It identifies modified functions and data flows, providing context for risk-aware code review.

How do I recommend targeted tests for high-risk code changes?▼

Recommend targeted tests for high-risk changes by verifying coverage status in existing test suites. Guided testing identifies gaps in coverage across components to ensure critical execution paths are tested.

Does automated risk analysis require existing test-coverage data to work?▼

Risk analysis applies to codebases that provide test-coverage data and change-detection outputs across components. This data is required to map changes to affected execution paths and verify coverage.

How do I structure code review findings by risk level?▼

Structure code review findings by grouping detected changes and their impacts according to risk level. This structured reporting details the specific modifications, coverage status, and recommended fixes.

Why does impact analysis require change-detection outputs across components?▼

Impact analysis requires change-detection outputs to identify modified functions and data flows across components. Without these inputs, the review cannot map changes to affected execution paths or assess risk accurately.

Related Skills

Explore More Software Engineering Skills→
AniTrendAniTrend
51

code-review-graph-review

Detect code changes and analyze impact radius for pull request reviews.

Official
Advanced
motormetricsmotormetrics
21

component-tester

Identify modified React components and execute their Vitest test suites.

Official
Intermediate
RheasilviaRheasilvia

Review Changes

Analyze code changes for risk and test coverage via knowledge graph.

Community
Advanced
yun520-1yun520-1
38

code-analyzer

Analyze codebases for architectural patterns, code quality, and DDD elements.

Community
Advanced