skills.rest
malinskibeniamin
malinskibeniaminCOMMUNITY
Explore all skills by this author →
GitHub

resilience-review

Identify edge-case failures in UI, forms, and data workflows from code diffs.

3|1|Updated Mar 23, 2026
Search Tags:#testing#validation#resilience#observability#edge-cases#risk-management#code-review
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill resilience-review-malinskibeniamin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resilience-review
Source: https://github.com/malinskibeniamin/skills/tree/main/resilience-review
Command: npx skills add https://github.com/malinskibeniamin/skills --skill resilience-review-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and block fragile behavior by identifying plausible unhappy paths, edge-case inputs, and state drift before code ships, enabling guardrails and observability.

Core Features & Use Cases

  • Structured risk surface and unhappy-path inventory for UI/forms, validation, async/data flows, state machines, and destructive actions.
  • Probes and defenses that enforce preconditions, invariants, postconditions, fallbacks, and observability.
  • A repeatable finding loop and governance artifacts to guide PR reviews.

Quick Start

Run resilience-review on a code diff to surface unhappy paths and generate a guardrails plan.

Frequently Asked Questions about resilience-review

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

FAQPage Schema
How do I identify edge-case failures in UI forms and async data flows during code changes?▼

To identify edge-case failures in UI forms and async data flows, run a resilience review on your code diff to surface unhappy paths and generate a standardized guardrails report. It enforces precondition, postcondition, fallback, and observability checks.

What is the best way to prevent state drift and fragile behavior in web application validation workflows?▼

The best way to prevent state drift and fragile behavior in validation workflows is to apply structured risk surface probing. This process inventories plausible unhappy paths and enforces invariants and fallbacks before code ships, producing governance artifacts for PR reviews.

How do I enforce precondition and postcondition checks for destructive actions in a pull request?▼

You can enforce precondition and postcondition checks for destructive actions by running a resilience review against the PR diff. It probes the changes for missing fallbacks and observability gaps, outputting a standardized resilience report to guide the review.

Does this resilience review approach work with state machines and asynchronous data workflows?▼

Yes, resilience review explicitly works with state machines and asynchronous data workflows. It detects plausible unhappy paths and edge-case inputs within these specific structures, applying checks to block fragile behavior and state drift.

Can I generate a standardized guardrails plan for code diffs touching destructive actions?▼

Yes, you can generate a standardized guardrails plan for code diffs touching destructive actions. Running the resilience review on the diff surfaces edge-case inputs and outputs a governance artifact detailing required defenses and observability checks.

Related Skills

Explore More Software Engineering Skills→
matrixoriginmatrixorigin
1.9k

mo-self-review

Automates code review and self-assessment for MatrixOne git working trees.

Official
Advanced
artofrawrartofrawr
1

code-review

Analyze code changes to enforce mandatory reviews before commits and deployments.

Community
Advanced
eventua11yeventua11y
1

writing-tests

Automate E2E and unit test setup and execution with Playwright and Vitest.

Official
Intermediate
multiversxmultiversx
12

mvx_property_testing

Generate property-based fuzz tests for MultiversX Rust smart contracts.

Official
Intermediate