skills.rest
erikhazzard
erikhazzardCOMMUNITY
Explore all skills by this author →
Website𝕏@erikhazzardGitHub

code__fixing-bugs

Diagnose defects by converting broken user journeys into executable integration tests.

1|1|Updated Mar 16, 2026
Search Tags:#fix#regression#integration-test#guardrails#contract-first#bug
One-click install
npx skills add https://github.com/erikhazzard/vasir --skill code-fixing-bugs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code__fixing-bugs
Source: https://github.com/erikhazzard/vasir/tree/main/.agents/skills/code__fixing-bugs
Command: npx skills add https://github.com/erikhazzard/vasir --skill code-fixing-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams diagnose and fix defects by turning broken user journeys into explicit, testable contracts and minimal, deterministic integration tests, preventing regressions.

Core Features & Use Cases

  • Define the broken journey contract before touching code.
  • Reproduce failures with a minimal integration test using real dependencies.
  • Apply the smallest safe fix and lock it with CI-ready guardrails.
  • Use for triaging defects, hunting regressions, and validating targeted fixes.

Quick Start

Describe the broken user journey, reproduce it with a minimal integration test, and apply the smallest safe fix.

Frequently Asked Questions about code__fixing-bugs

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

FAQPage Schema
How do I fix bugs by turning broken user journeys into integration tests?▼

To fix bugs with this approach, you first define the broken journey contract, reproduce the failure using a minimal integration test with real dependencies, and then apply the smallest safe fix locked by deterministic guardrails.

What is a contract-first test for diagnosing software regressions?▼

A contract-first test for diagnosing regressions explicitly defines the expected behavior of a user journey before touching code. This test acts as a deterministic guardrail to reproduce failures and validate targeted fixes across services.

How do I reproduce a defect with a minimal integration test using real dependencies?▼

You reproduce a defect by identifying the exact broken user journey and writing a minimal integration test that executes it against real dependencies. This enforces minimal repro steps to isolate the failure before applying a fix.

When should I use integration-test-first workflows for bug triage?▼

You should use integration-test-first workflows for bug triage when you need to hunt regressions or validate targeted fixes across services. It enforces minimal repro steps and deterministic guardrails to ensure durable defect resolution.

Can I use this contract-first approach to fix defects across multiple services?▼

Yes, you can use this contract-first approach to fix defects across services with real dependencies. It applies targeted fixes by turning broken user journeys into executable contracts and running deterministic integration tests.

Why use deterministic guardrails when applying a minimal safe fix?▼

Deterministic guardrails prevent future regressions by locking the minimal safe fix with CI-ready tests. They ensure the newly defined contract for the user journey remains executable and validated against real dependencies.

Related Skills

Explore More Software Engineering Skills→
roberttmadsen13-delroberttmadsen13-del

customer-journey-map

Document and visualize customer journeys across stages, touchpoints, emotions, and KPIs.

Community
Advanced
docs-plusdocs-plus
88

diagnose

Diagnose complex software bugs through a structured 6-phase debugging workflow.

Official
Advanced
espensevespensev

qa

Validate code changes against the planning contract and run tests.

Community
Advanced
Nathanto-aiNathanto-ai

black-box-red-testing

Generate deterministic adversarial red tests targeting distinct bug hypotheses.

Community
Advanced