From frontend-skills
Reviews code changes for resilience: identifies unhappy paths, edge cases, error handling, fallbacks, and state management gaps. Use before commit/PR to surface failure scenarios.
How this skill is triggered — by the user, by Claude, or both
Slash command
/frontend-skills:resilience-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Repo/code changes: run `/deslop` before commit, push, PR, or merge.
Repo/code changes: run /deslop before commit, push, PR, or merge.
Murphy pass: find every plausible unhappy path, then block, guard, recover, observe.
Run /resilience-review for diffs touching forms, validation, submit, async/data, mutations, cache, retries, state machines, mode/union switches, config/resource choice, destructive actions, or loading/empty/error/success UI.
Skip docs/test/style/trivial pure logic only; record reason.
## Resilience review
Risk surface:
- ...
Failure matrix:
| Scenario | Trigger | Expected behavior | Guard | Test | Observability |
Finding queue:
| Finding | Repro/diagnosing-bugs loop | RED test or snapshot | Owner | Visual review needed |
Required tests:
- ...
Polish gaps:
- ...
Verdict: PASS | NEEDS_GUARDS | BLOCKED
Rules: cite files/routes/forms/API. Docs/help text not enough when code can prevent bad state. Real gap unfixed -> PR evidence with owner/deferral.
See REFERENCE.md.
npx claudepluginhub redpanda-data/ui-harness --plugin frontend-skillsFailure-mode audit (FMEA for software) — for each way the system can fail (network, storage, partial completion, crash, concurrency, bad input), check whether code DETECTS, HANDLES, RECOVERS, and COMMUNICATES it. Triggers on: "/resilience-audit", "resilience-audit", "FMEA audit". Use when touching network, storage, async, retry, or rollback paths. Flags data loss, silent-success-on-failure, missing rollback/retry/idempotency. Reports; does not fix unless asked.
Reviews code for bugs, security issues, performance problems, and correctness. Delegates fixes, tests, and security scans to specialized skills. Triggers on PRs and significant code changes.
Stress-tests code adversarially to uncover edge cases, security holes, race conditions, and logical flaws missed by normal reviews. Use before deploying critical code handling user input or external data.