
Idempotent Redundancy
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.
Install
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill idempotent-redundancyWhat is this skill?
- 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
Adoption & trust: 1 installs on skills.sh; 3.8k GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
Recommended Skills
Journey fit
Ship review is the canonical shelf because redundancy patterns are most dangerous right before merge and production—when fallbacks multiply writers. Review covers idempotency checks on defensive code paths, not greenfield feature design alone.
Common Questions / FAQ
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.
SKILL.md
READMESKILL.md - Idempotent Redundancy
# 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: true` for 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"