change-risk-review

Reviews git diffs for behavior, protocol, and architecture risks before commit.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/c2kaka/fancy-skills --skill change-risk-review-c2kaka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-risk-review
Source: https://github.com/c2kaka/fancy-skills/tree/main/skills/change-risk-review
Command: npx skills add https://github.com/c2kaka/fancy-skills --skill change-risk-review-c2kaka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted coding produces fast diffs that are hard to review for hidden risks: behavior regressions, protocol field changes, architecture constraint violations, and hallucination-driven errors. This Skill turns a raw git diff into a structured risk review and, only after user confirmation, a classified commit message that PR reviewers can trust. ## Core Features & Use Cases - Seven-question risk review: Covers behavior changes, affected existing features, protocol/field changes, golden-test verification adequacy, AI uncertainty and hallucination risk types, change diffusion path, and architecture constraint breaches. - Four-tier risk classification: Classifies changes as Tuning, Behavior change, Protocol change, or Architecture change with review levels from Low to High, adopting the highest level when categories overlap. - Gated commit workflow: Never commits on the first pass; only commits after explicit user confirmation, then writes a commit message with classification, impact scope, verification evidence, and residual uncertainty. - Use Case: Before committing an AI-generated change to a planner routing module, run the review to surface that a session protocol field changed, note missing golden-test coverage, and produce a Medium-high classified commit message. ## Quick Start Ask the agent to review the current git changes for risk classification and then, after you confirm, write a classified commit message.

Frequently Asked Questions about change-risk-review

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

FAQPage Schema
How do I review AI-generated code changes before committing?▼

Run the review on your current git diff to get a structured report covering behavior changes, affected features, protocol changes, test adequacy, and architecture breaches. The change is classified into Tuning, Behavior, Protocol, or Architecture categories with a corresponding review level.

How to write a commit message that classifies change risk?▼

After confirming the review, the commit message includes a classification header with review level, per-category change details, impact scope, change diffusion path, verification commands run, and residual AI uncertainties. This gives PR reviewers the context without reading the full diff.

What hallucination risks does AI code review check for?▼

The review checks three hallucination risk types: business-semantic errors where project definitions differ from generic understanding, boundary-condition errors missing concurrency or partial-failure cases, and dependency-cognition errors where actual dependency behavior differs from documentation.

Does the skill commit changes automatically after review?▼

No. The first pass only produces the risk review. A commit happens only when the user confirms the review is acceptable and explicitly asks to commit, and the staged file set is verified before committing.

When is a change classified as high risk in code review?▼

A change is High risk when it alters responsibility boundaries, call chains, lifecycle, or state ownership of core components like Planner, Skill, Action, Runtime, Memory, or Tool. High-level changes require human confirmation of design intent, ideally with a design note or ADR.