skills.rest
paulnsorensen
paulnsorensenCOMMUNITY
Explore all skills by this author →
GitHub

pasteurize

Reproduce reported bugs and apply minimal regression-protected fixes.

15|1|Updated May 4, 2026
Search Tags:#debugging#root cause analysis#agent workflow#instrumentation#regression testing#test harness#performance regression
One-click install
npx skills add https://github.com/paulnsorensen/easy-cheese --skill pasteurize
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pasteurize
Source: https://github.com/paulnsorensen/easy-cheese/tree/main/skills/pasteurize
Command: npx skills add https://github.com/paulnsorensen/easy-cheese --skill pasteurize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

pasteurize helps you harden debugging by converting a reported failure into a deterministic feedback loop, reproducing the bug, identifying the cause, and producing a regression-protected minimal fix.

Core Features & Use Cases

  • Deterministic bug feedback loop: builds a pass/fail signal (failing test, CLI/HTTP repro, scripted UI replay, or trace replay) so the failure can be iterated on quickly.
  • Root-cause driven remediation: runs a six-phase loop (feedback loop → reproduce → hypothesise → instrument → fix + regression test → cleanup) with falsifiable ranked hypotheses.
  • Regression safety & cleanup: writes the regression test first, applies the smallest production change, verifies the original repro no longer fails, and removes debug instrumentation.

Quick Start

Run /pasteurize when you have a failing test, stack trace, or repro steps for an issue you want diagnosed and fixed with a regression test.

Frequently Asked Questions about pasteurize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix flaky tests and performance regressions with a reproducible feedback loop?▼

Root cause analysis for unexplained software behavior requires constructing a deterministic test harness or CLI repro, instrumenting targeted traces, and verifying ranked falsifiable hypotheses against the failure signal.

What is the best way to debug a visible misbehavior when I have stack trace repro steps?▼

Targeted instrumentation for debugging hard bugs requires inserting trace tags into a scripted UI replay or test harness, verifying the failure signal, and removing all debug tags after applying the minimal production fix.

Do I need a failing test or repro steps to diagnose and fix unexplained wrong behavior?▼

Yes, you need a failing test, stack trace, CLI/HTTP repro, or failure signal to build a deterministic pass/fail loop for iterating on the bug and producing a regression-protected minimal fix.

Can I use regression testing to harden debugging for flaky tests and unexplained failures?▼

Yes, regression testing hardens debugging by writing the test first, applying the smallest production change, verifying the original repro no longer fails, and removing debug instrumentation during cleanup.

Related Skills

Explore More Software Engineering Skills→
TrebuchetDynamicsTrebuchetDynamics
5

diagnose

Diagnose hard bugs and performance regressions through an evidence-driven feedback loop.

Official
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
OrestesKOrestesK
2

diagnose

Diagnose software bugs and performance regressions through a disciplined feedback loop.

Community
Advanced
juliuss1907juliuss1907

systematic-debugging

Automate root cause analysis and systematic debugging across four investigation phases.

Community
Advanced