Review distributed-systems code diffs for correctness and operability hazards.
npx skills add https://github.com/austintheriot/dotfiles --skill distsys-review
Please help me install this Agent Skill. Skill: distsys-review Source: https://github.com/austintheriot/dotfiles/tree/main/.claude/skills/distsys-review Command: npx skills add https://github.com/austintheriot/dotfiles --skill distsys-review
Prevents subtle distributed-systems correctness and operability failures that often slip past tests by reviewing changed code for failure modes that only appear under partial outage, retries, or scale.
Run distsys-review on your current branch diff so it checks for distributed-systems footguns in the changes.
High-intent search queries and answers about installing and using this skill.
Analyze branch diffs against main to detect distributed systems correctness hazards. The review checks changed code for failure modes like retries without idempotency, missing fencing tokens, and replication-lag races, providing severity-labeled findings with file:line references.
Distributed systems code reviews should target retries without idempotency, unbounded queues, missing fencing tokens, replication-lag races, and cache stampedes. These cross-process hazards often slip past standard tests and fail under partial outage or scale.
Yes, distributed systems code review supports targeted file paths, PR numbers, and git ranges. By default it analyzes the current branch diff against main, allowing you to scope the review to specific changes.
It reviews code changes to detect operability hazards likely to fail under partial failure, retries, or scale. The process applies category-based findings with severity labels and delegates deeper runtime or data-model questions to specialized subagents.
No, the distributed systems review avoids comment posting. It generates actionable, non-chatty reports with file:line references and severity labels, keeping the feedback contained to the review workflow.
You need to check for idempotency and fencing tokens whenever changed code involves retries or cross-process coordination. Reviewing these mechanisms early prevents subtle correctness failures that only appear during partial outages or network retries.
austintheriotReview code diffs for data-flow, state-ownership, and boundary mismatches.
nesnilnehcIdentify language and runtime conformance issues in C# and F# code.
archyl-comAnalyze code changes against Archyl's C4 model and conformance rules.
rodrigo-altissimoGuide distributed system design and review for correctness under partitions, failures, and retries.
