/pasteurize

A discipline for hard bugs. Skip phases only when explicitly justified.

When exploring the codebase, call the selected source-code backend directly according to code-intelligence-routing.md, and check .cheese/specs/ for any spec or design notes that touch the failing seam.

Portability reference: ../cheese/references/harness-portability.md. It covers helper resolution, sub-agent dispatch, GitHub operations, and handoff transitions; prefer the bundled or repo-local helper first, and treat ${CLAUDE_SKILL_DIR} as optional host-provided fallback. The handoff blocks below are the portable contract; slash commands are host renderings, not the control model.

Phase 1 — Feedback loop

This is the skill. Everything else is mechanical. If you have a fast, deterministic, agent-runnable pass/fail signal for the bug, you will find the cause — bisection, hypothesis-testing, and instrumentation all just consume that signal. If you don't have one, no amount of staring at code will save you.

Spend disproportionate effort here.

Ways to construct one

To pick a loop shape, see references/feedback-loops.md for the ten-option ordered menu.