gabrielbchacon

Log Incident — Development skill for Claude Code

Development community

Record an incident, bug or unexpected behaviour in kb/incidents/.

How to install Log Incident

Installs to ~/.claude/skills/gabrielbchacon-ai-dev-bootstrap-log-incident/SKILL.md

Terminal
mkdir -p ~/.claude/skills/gabrielbchacon-ai-dev-bootstrap-log-incident && curl -fsSL https://raw.githubusercontent.com/gabrielbchacon/ai-dev-bootstrap/HEAD/commands/log-incident.md -o ~/.claude/skills/gabrielbchacon-ai-dev-bootstrap-log-incident/SKILL.md

Restart Claude Code, or start a new session, for it to be picked up.

What Log Incident does


description: Record an incident, bug or unexpected behaviour in kb/incidents/

Invoke the `kb-note` skill to write an incident record.

Ask for, and do not invent: the symptom exactly as observed (exact error text, exact command, exact input), the root cause, the fix, and something **executable** that prevents recurrence.

Two rules that get broken most often here:

  • If the root cause is not actually known, say so and keep status: open. A plausible guess recorded as a cause is how t

Alternatives in Development

  • Om Dump — Freeform capture mode 4.6k ★
  • /report — Generate a submission-ready bug bounty report 1.8k ★
  • Opik Openclaw — 🦞 Official plugin for OpenClaw that exports agent traces to Opik 725 ★

Full documentation available on GitHub

View Source Repository