insforge-debug

# InsForge Debug Diagnose problems in InsForge projects by combining the backend's observability primitives — logs, metrics, db-health, advisor, policies, metadata, error objects, deploy state, and AI assist. This skill provides: 1. A reference per **debug primitive** (one observability surface each — under `references/`) 2. **Symptom Recipes** (below) that name the primitive sequence for known reactive symptoms and proactive audits **Always use `npx -y @insforge/cli`** — never install the CLI globally. ## Fastest Path: AI-Assisted Triage When the user gives a concrete description (error message, failing URL, HTTP status), hand it to the InsForge debug agent. Unlike the other primitives, this one returns suggestions, not just observations — verify the diagnosis against the primitives it cites before acting on it. ```bash npx -y @insforge/cli diagnose --ai "<issue description>" ``` See [references/ai-assisted.md](references/ai-assisted.md) for when to use this first vs when to skip, and how to verify the output. ## Debug Primitives Each primitive is one independently-queryable observability surface backed by a distinct underlying data source. Real diagnoses are compositions of primitives. All commands run via `npx -y @insforge/cli ...`. The `(command)` shown next to each primitive is the actual CLI command — primitive names are concept labels, **not** CLI subcommand names (e.g., "DB health" is `diagnose db`, not `diagnose db-health`; "Policies" is `db policies`, not ...