skills.rest
BicameralAI
BicameralAIOFFICIAL
Explore all skills by this author →
GitHub

bicameral-reset

Perform two-step dry-run and confirm resets of polluted ledgers.

Updated Aug 27, 2026
Search Tags:#audit#ingestion#data-integrity#reset#safe#ledger
One-click install
npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-reset
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bicameral-reset
Source: https://github.com/BicameralAI/bicameral-mcp/tree/main/.claude/skills/bicameral-reset
Command: npx skills add https://github.com/BicameralAI/bicameral-mcp --skill bicameral-reset

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Emergency trust recovery for a polluted or stale ledger. Fires when the user says "my ledger looks wrong", "nuke the ledger", "start over", "this is polluted", or otherwise loses trust in the current state. DRY RUN BY DEFAULT — always confirms with the user before the destructive call.

Core Features & Use Cases

  • Two-step safety: dry-run returns a wipe plan with cursors_before and replay_plan, then confirm executes the wipe only after explicit user consent.
  • Scoped to repo: wipes only rows for the active repository, preserving other projects.
  • Re-ingest guidance: provides a replay plan to rebuild the ledger by re-running original ingest calls.

Quick Start

Ask it to perform a dry-run reset to preview the wipe, then confirm to execute the ledger reset and replay ingestion from the plan.

Frequently Asked Questions about bicameral-reset

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

FAQPage Schema
How do I safely reset a polluted ledger without losing data integrity?▼

A safe ledger reset uses a two-step process: a dry run generates a wipe plan with cursors and a replay plan, then explicit confirmation executes the scoped wipe. This ensures data integrity and auditability before destructive changes.

What happens during a dry run before a ledger wipe?▼

A dry run for a ledger wipe returns a plan containing cursors_before and a replay_plan for re-ingestion. No destructive actions occur until you explicitly confirm, ensuring full visibility into what will be removed.

Can I reset the ledger for just one repository without affecting other projects?▼

Yes, a ledger reset is scoped to the current repository. The wipe only removes rows associated with the active project, preserving the ledger data and trust state for all other repositories.

How do I rebuild the ledger after a full wipe?▼

After a full ledger wipe, rebuild by following the provided replay plan to re-run original ingest calls. This re-ingestion guidance restores the ledger state using the captured cursors and historical ingestion data.

When should I perform a full ledger reset instead of patching data?▼

A full ledger reset is appropriate when trust is broken, the ledger shows drift, or mismatches appear after ingestion and cannot be easily patched. It provides an auditable wipe and replay to restore trust.

Does the ledger reset require explicit user consent before deleting rows?▼

Yes, the ledger reset enforces a two-call pattern that requires explicit user consent. The destructive wipe call only executes after the user reviews the dry run output and actively confirms the action.

Related Skills

Explore More Software Engineering Skills→
acertainKnightacertainKnight
12

Paper Discovery

Discover and curate scholarly papers across arXiv, PubMed, Semantic Scholar, and OpenAlex.

Community
Advanced
OmarHosamCodesOmarHosamCodes
1

wiki-rebuild

Archive, rebuild, and restore a wiki from sources with safety checks.

Community
Advanced
kucherenkokucherenko
71

laundering

Merge territory branches, run verification, and update ledger entries for releases.

Community
Advanced
robit-manrobit-man

doc-sync

Synchronize documentation with codebase through automated drift audits and fixes.

Community
Advanced