bedrock

Audit codebase foundations with adversarial stress tests and record findings in an AUDIT.md ledger.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/kennykankush/skillpack --skill bedrock-kennykankush
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bedrock
Source: https://github.com/kennykankush/skillpack/tree/main/plugins/workbench/skills/bedrock
Command: npx skills add https://github.com/kennykankush/skillpack --skill bedrock-kennykankush

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bedrock provides a disciplined, adversarial audit mode for codebases, enabling engineers to stress-test load-bearing logic, surface fragility, and produce actionable reports backed by runnable repros. It maintains an AUDIT.md ledger at the repository root to track findings across runs and ensures traceability of inspection outcomes.

Core Features & Use Cases

  • Adversarial foundation audits: systematically stress critical paths to reveal fragility and architectural weaknesses.
  • Ledger-driven reporting: maintain an AUDIT.md ledger to map findings, regressions, and verified cures across iterations.
  • Modes & scope: supports default Report mode and Report-then-fix for controlled hardening after deep inspection; covers entire codebases or focused subsystems.
  • Use Case: after a large build sprint, run Bedrock to verify core foundations before a release and generate a determinable fragility report.

Quick Start

Ask your agent to run Bedrock in Report mode to audit the foundations and generate a fragility report.

Frequently Asked Questions about bedrock

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit codebase foundations and surface hidden fragility before a release?

A foundation audit systematically stress-tests load-bearing logic to surface hidden fragility. It executes reproducible probes against your repository and records the findings into a traceable AUDIT.md ledger for actionable remediation.

What is a fragility audit ledger and how does it track codebase weaknesses?

A fragility audit ledger is an AUDIT.md file maintained at the repository root to track codebase weaknesses. It maps findings, regressions, and verified cures across iterations to ensure traceable inspection outcomes.

Can I run a focused code audit on specific subsystems instead of the entire repository?

Yes, you can run a focused code audit on specific subsystems instead of the entire repository. The audit supports targeted scopes while still executing stress tests, running probes, and updating the AUDIT.md ledger.

Does a code audit require specific dependencies or host environments to run probes?

A code audit requires safe, host-agnostic tooling to run probes and has no external dependencies. It operates directly within your environment to execute stress tests and generate the fragility report.

What is the best way to fix code fragility identified during an audit?

The best way to fix code fragility identified during an audit is to use Report-then-fix mode. This mode enables controlled hardening by applying remediation directly after deep inspection of the recorded findings.