anvi:debug

Files (1)

• SKILL.md

SKILL.md (first lines)

# /anvi:debug — Cognitive Debugging

## Arguments

$ARGUMENTS

## Process

Execute the debug workflow from `~/.claude/anvi/workflows/debug.md`.

### 1. Load cognitive OS

Read these files to load the cognitive operating system:
1. `~/.claude/anvi/cognitive-os/base-layer.md` — passive checks on every action
2. `~/.claude/anvi/cognitive-os/modes/diagnose.md` — primary lens for debugging
3. `~/.claude/anvi/cognitive-os/translation.md` — output translation rules
4. `~/.claude/anvi/cognitive-os/adaptive-observation.md` — lens chaining, depth control, boundary-pair observation, composition verification

### 2. Load project catalogues (if they exist)

Not by reading the catalogue files whole — on a mature project they run to megabytes.
The debug workflow delivers them by the files the bug involves
(`node "$HOME/.claude/anvi/scripts/boundary-entries.js" --file=<path>`): error patterns (check FIRST before
investigating), invariants (the bug may be a violation), lifecycles (timing bugs are
immediately classifiable), with a counts line said to the user every time.

### 3. Execute the debug workflow

Follow `~/.claude/anvi/workflows/debug.md` to:
- Pre-check catalogues for known patterns matching the symptoms
- Spawn the `anvi-debugger` agent with cognitive OS loaded
- Collect root cause diagnosis
- Post-resolution: append new patterns/invariants/lifecycles to `.anvi/` catalogues

## Critical Rules

1. **Never surface Sanskrit terms to the user.** Use the translation layer.
2. **Diagnose lens is primary.** Follow the cognitive chain: gather → classify → scan boundaries → compress → prove → fix → ship.
3. **Catalogues grow silently.** When a new error pattern, invariant, or lifecycle is discovered, append it to `.anvi/` without announcing it.
4. **One pass or the architecture fails.** If the cognitive chain works, root cause should be found without workaround attempts.

From MrityunjayBhardwaj/anvi, GPL-3.0.

More from MrityunjayBhardwaj/anvi