Idempotent Redundancy
- 466 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
idempotent-redundancy is an agent skill that enforces idempotent patterns when adding fallback paths, repair hooks, and belt-and-suspenders logic so redundant code stays safe to rerun without loops or data corruption for
About
idempotent-redundancy is a Code Review & Quality skill from parcadei/continuous-claude-v3 (user-invocable: false) that agents apply when adding redundant paths such as fallbacks and repair hooks. The skill mandates idempotent operations: use _is_merge for Braintrust updates, check values before writing in fallbacks, atomic write/rename for files, and reconciliation steps safe to run repeatedly. It explicitly forbids unconditional writes in fallback paths, competing writers, and repair actions that trigger more repairs. Developers reach for idempotent-redundancy when agents add belt-and-suspenders logic that must not cause loops, churn, or data corruption on repeated execution.
- DO/DON'T rules for redundant paths: idempotent fallbacks only
- Braintrust updates must use `_is_merge: true`
- Fallback writes only when values are missing—no unconditional repair churn
- Atomic write/rename for files; reconciliation safe to run repeatedly
Idempotent Redundancy by the numbers
- 466 all-time installs (skills.sh)
- +4 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #244 of 1,382 Code Review & Quality skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill idempotent-redundancyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 466 |
|---|---|
| repo stars | ★ 3.9k |
| Security audit | 3 / 3 scanners passed |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do you make agent fallback paths idempotent?
Install this when your agent adds fallbacks, repair hooks, or belt-and-suspenders paths so redundant logic stays safe to rerun without loops or corruption.
Who is it for?
Developers whose agents add fallback logic, repair hooks, or redundant write paths that must be safe to rerun without loops or corruption.
Skip if: Simple linear code paths without fallbacks, retries, or redundant writers do not need idempotent-redundancy guardrails.
When should I use this skill?
An agent adds fallback paths, repair hooks, belt-and-suspenders logic, or redundant write operations that could loop or corrupt data on rerun.
What you get
Idempotent fallback implementations with merge-safe updates, pre-write existence checks, and atomic file operations that survive repeated execution.
- Idempotent fallback implementations
- Safe reconciliation routines
Files
Idempotent Redundancy
When adding redundant paths (fallbacks, belt-and-suspenders), make them idempotent.
Pattern
Redundancy without idempotency causes loops, churn, or data corruption.
DO
- Use
_is_merge: truefor Braintrust updates - Check if value exists before writing (fallback only if missing)
- Use atomic write/rename for file operations
- Make reconciliation steps safe to run repeatedly
DON'T
- Write unconditionally in fallback paths
- Allow multiple writers to overwrite each other
- Fire "repair" actions that can trigger more repairs
Source Sessions
- a541f08a: "Redundancy is good only if idempotent"
- 1c21e6c8: "Belt-and-suspenders, but make it idempotent"
- 6a9f2d7a: "Idempotent repair hooks"
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.531k185k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.260k92.5kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.233k185kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.210k92.5k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.178k260kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.167k185kFAQ
Why is idempotent-redundancy needed for fallbacks?
idempotent-redundancy prevents redundant fallback and repair paths from causing loops, churn, or data corruption. Without idempotency, multiple writers and unconditional fallback writes can overwrite each other or trigger cascading repairs.
What patterns does idempotent-redundancy require?
idempotent-redundancy requires _is_merge for Braintrust updates, existence checks before fallback writes, atomic write/rename for files, and reconciliation steps safe to run repeatedly. Unconditional writes and competing repair actions are forbidden.
Is Idempotent Redundancy safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.