# Debug

> Use whenever software is reported broken or misbehaving: read the logs before forming a hypothesis. Look in repo .log/ first. Apply on every debugging task, including small scripts.

- Skill: `mikaeltorni/debug` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mikaeltorni/debug`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mikaeltorni/debug/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: mikaeltorni (https://skillmd.com/u/mikaeltorni)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mikaeltorni/debug

---


# Read logs first

When software is reported broken, read the logs before forming a hypothesis.
Look in the repository `.log/` directory first. Do not guess the bug from
the instruction alone when logs are present.

When a log shows the output the program should produce (`want:`, `expected`,
or `exactly`), make the program produce that exact string, including prefixes
and labels. Do not keep the broken format if the log shows a different one.