SkillVaultskills Browse all 1,000+ skills

Code Quality · Version 1.1.0 · Reviewed 2026-08-02

Functional Change Risk Reviewer

Make a defensible decision about functional diff review and runtime failure analysis with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 4 diagnostic checks 7 quality gates

Finds runtime correctness, contract, concurrency, validation, and distributed configuration risks introduced by a change. It grounds the decision in the base diff, callers, contracts, state transitions, configuration producers and consumers, and negative-path tests and explicitly prevents reviewing changed lines in isolation while the failure occurs in an unchanged caller or independently deployed consumer.

₹199 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools.

What this skill helps you do

  • Functional diff review
  • Runtime failure analysis
  • Contract change assessment

How Functional Change Risk Reviewer works

You provide

The code, its invariants, and how failures currently surface

It inspects

Error paths and lifetime handling for functional diff review

It decides

A runtime failure analysis change that makes invalid states unrepresentable

You verify

A deliberately invalid input fails clearly at the boundary

What it checks first

Functional Change Risk Reviewer finds runtime correctness, contract, concurrency, validation, and distributed configuration risks introduced by a change. It grounds the decision in the base diff, callers, contracts, state transitions, configuration producers and consumers, and negative-path tests and explicitly prevents reviewing changed lines in isolation while the failure occurs in an unchanged caller or independently deployed consumer. Use it when the work involves Functional diff review, Runtime failure analysis, Contract change assessment.

  1. Whether errors are handled where they can be resolved or merely passed upward with less context.
  2. Whether types make invalid states unrepresentable or merely document intent.
  3. Ownership and lifetime of resources, and whether every path releases what it acquired.
  4. Whether abstractions hide complexity or relocate it somewhere harder to inspect.

Failure modes it recognizes

  • A caught exception logged and swallowed, allowing execution to continue with invalid state.
  • Error types collapsed into a single generic type, losing the ability to handle cases differently.
  • Nullable fields encoding several distinct meanings, forcing every caller to guess.
  • A helper abstraction with one caller, which adds indirection without removing duplication.
  • Silent coercion masking a type mismatch until it surfaces as corrupt data.

Answers it will reject

  • Rewriting for elegance without a behavioral test suite, which converts known code into unknown risk.
  • Adding a lint rule to enforce a pattern nobody has justified.
  • Treating warnings as noise, which trains the team to ignore the one that matters.

Decision rules it applies

  • Fail fast on invalid state rather than continuing with a defaulted value.
  • Encode invariants in types and constraints where the language allows it.
  • Prefer local clarity over global cleverness; the reader is the constraint.

Evidence it asks for

  • Confirm each error path is exercised by a test rather than assumed correct.
  • Check that a deliberately invalid input produces a clear failure at the boundary.
  • Compare behavior before and after refactoring with characterization tests.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to functional diff review.
  2. Trace concrete failure or abuse paths for runtime failure analysis; do not report checklist items without a mechanism.
  3. Prioritize contract change assessment findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Functional diff review assessment
  • Runtime failure analysis decision and action plan
  • Contract change assessment verification checklist

Evidence requirements

  • Functional and quality requirements
  • Scale, latency, consistency, cost, and compliance constraints
  • Current topology and alternatives considered

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Apply the functional change risk reviewer to our current functional diff review work. We need a concrete decision, bounded changes, and evidence that the result is correct.

Expected output

Start with the base diff, callers, contracts, state transitions, configuration producers and consumers, and negative-path tests. The highest-risk failure is reviewing changed lines in isolation while the failure occurs in an unchanged caller or independently deployed consumer. Trace changed decisions through their runtime consumers and rank findings by reachability and user impact. Verify the result by building a failing test or reproduction for every blocking finding and confirming accepted counterexamples stay valid.

Boundaries and compatibility

Ideal for

  • Functional diff review: produce a decision or artifact grounded in supplied evidence.
  • Runtime failure analysis: produce a decision or artifact grounded in supplied evidence.
  • Contract change assessment: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Producing a generic reference architecture without requirements
  • Hiding material trade-offs behind best-practice language

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.