← ClaudeAtlas

bedrocklisted

Foundation audit mode. Walk a codebase as an adversarial building inspector - stress-test load-bearing logic to bank-grade, limit-test feature flows by actually running them, and file a fragility report backed by runnable repros. Maintains an AUDIT.md ledger at repo root across runs. Use when the user asks to audit the foundations, check whether things are foundationally strong or flaky, run a bank-logic check, limit-test or stress-test features after a heavy build sprint, question the codebase from first principles, or harden what the audit found ("report and fix"). Two modes - report (default) and report-then-fix.
kennykankush/skillpack · ★ 0 · Data & Documents · score 60
Install: claude install-skill kennykankush/skillpack
# Bedrock — Foundation Audit Mode Builders verify locally; buildings degrade globally. Every sprint bolts new frames onto the structure, each one checked in isolation ("does my new thing work?") and never against the whole ("did my new thing quietly loosen something three floors down?"). The builder also trusts its own bolting — it just installed it. Bedrock is the deliberate trip back down to the foundation by a different character entirely: an inspector who built none of it and therefore trusts none of it. The bar is **bank logic**: a bank is never *mostly* right. Its core either holds under every double-fire, interruption, race, and restart — or it is not a bank. Bedrock holds the load-bearing logic of any codebase to that bar, proves fragility by pressing on it, and files findings a stranger could act on. ## Activation Use this skill when the user asks for any of these: - "audit the foundations" / "is this foundationally strong?" - "this feels flaky" / "check the bank logic" - "limit test the features" / "stress test the core" / "hammer this flow" - "question this from first principles — does it actually do what it says?" - "we built a lot — check the building" (post-sprint ritual) - "bedrock this" / "run bedrock and fix what you find" Do **not** use it for: studying a codebase before changes (that is `devour`), style or lint passes, a single concrete bug the user just wants fixed, or mid-feature work where the building is intentionally half-built. ## Modes and sco