code-review-error-handling

code-review-error-handling is a skill for Claude Code, Codex from randomm/pi-ensemble. It costs 33 tokens per session (2,591 once invoked), scanned A, original, Apache-2.0.

A code-review checklist focused on how software detects, reports, and recovers from errors.

In plain words
What is it for?
It is for reviewing error propagation, exceptions, timeouts, retries, partial failures, cleanup, and diagnostic context.
Why use it?
It helps catch failures that are hidden, poorly reported, or leave only part of an operation completed.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/randomm/pi-ensemble/code-review-error-handling
Any agent
npx skills add randomm/pi-ensemble --skill code-review-error-handling
Clone the repo
git clone --depth 1 https://github.com/randomm/pi-ensemble

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for code-review-error-handling

README.md
[![agentmods](https://agentmods.dev/badge/skills/randomm/pi-ensemble/code-review-error-handling.svg)](https://agentmods.dev/skills/randomm/pi-ensemble/code-review-error-handling)
Your own site
<a href="https://agentmods.dev/skills/randomm/pi-ensemble/code-review-error-handling"><img src="https://agentmods.dev/badge/skills/randomm/pi-ensemble/code-review-error-handling.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,591 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.02591
Opus 5 $0.00016 $0.01295
Sonnet 5 $0.00007 $0.00518
Haiku 4.5 $0.00003 $0.00259

Measured 3d ago against content hash 37e91d103771, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-review-error-handling scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skill/code-review-error-handling/SKILL.md · 155 lines

How it starts

The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Review: Error Handling Lens

Specialized agent for error-handling and resilience analysis during code review. Focuses on how the code signals, propagates, contains, and recovers from failure — and whether failure leaves the system in a consistent, observable state.

Scope Discipline

When PM explicitly dispatches this lens:

  • ✅ Review error-signalling discipline: ignored return codes, suppressed results, unchecked error types
  • ✅ Analyze exception/error hygiene: overbroad catches, empty catches, swallowed errors, lost stack traces
  • ✅ Check propagation: errors surfaced at the correct layer, not buried beneath
  • ✅ Verify timeout and cancellation discipline on all external I/O
  • ✅ Verify retry semantics: bounded attempts, backoff, idempotency under replay
  • ✅ Verify partial-failure handling in batch / multi-step operations
  • ✅ Verify error observability: caught errors carry enough context to diagnose
  • ✅ Verify resource cleanup on error paths (handles, locks, connections)

Do NOT broaden into:

  • ❌ Security vulnerabilities per se (use SECURITY lens) — but note: error leakage that reveals internals to callers is a SECURITY cross-lens concern
  • ❌ Type correctness (use TYPE_SAFETY lens)
  • ❌ Raw throughput / algorithmic cost (use PERFORMANCE lens) — but note: unbounded retries with no backoff is a resilience concern, flag here
  • ❌ Structural coupling / SRP (use ARCHITECTURE lens) — but note: transactional-vs-external-store boundary issues are ARCHITECTURE territory; if in doubt, flag with cross_lens_candidate=true
  • ❌ Readability (use SIMPLICITY lens)

Output Format

All findings must follow this structure:

## Must Fix
- [CRITICAL|HIGH] [path:line] Title
  - Description: What is wrong and why it matters
  - Suggestion: Specific fix with code example
  - Metadata: cross_lens_candidate=true/false, tradeoff_required=true/false

## Observations
- [MEDIUM|LOW] [path:line] Title
  - Description: Informational finding
  - Metadata: cross_lens_candidate=true/false, tradeoff_required=true/false

## Summary
[One paragraph overall assessment]

Read the full file on GitHub · 155 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 155 lines · 33 tokens per session scan A 37e91d103771

Subscribe to this mod's changes

code-review-error-handling is a skill published in the GitHub repository randomm/pi-ensemble (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 33 tokens to every session and 2,591 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens