fix

Diagnose bugs and guide user-confirmed fixes across code layers.

5|2|Updated Dec 11, 2025

Search Tags:#testing #architecture #debugging #memory #diagnostics #hypothesis #root-cause

Ready to run

npx skills add https://github.com/thoreinstein/opencode-config --skill fix-thoreinstein

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/thoreinstein/opencode-config/tree/main/skill/fix
Command: npx skills add https://github.com/thoreinstein/opencode-config --skill fix-thoreinstein

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and fix bugs with architecture-aware analysis and a diagnostic-first approach.

Core Features & Use Cases

Diagnostics-first analysis guides architecture review, data-model checks, and instrumentation.
Hypothesis generation & distillation yields 1-2 root causes with evidence.
Cross-project memory leverages past patterns to accelerate resolution.
User-confirmed fixes & thorough testing ensure safe, documented changes.

Quick Start

Use the fix skill to describe a bug and start the guided workflow. For example, submit a command like: /fix "UI not updating after API call"

Frequently Asked Questions about fix

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

FAQPage Schema

How do I diagnose a bug's root cause across frontend and backend layers?▼

To diagnose a bug's root cause across layers, use a diagnostics-first process that guides context gathering, generates hypotheses, and distills evidence into validated root causes using architecture docs and data-model checks.

What is architecture-aware analysis for debugging?▼

Architecture-aware analysis for debugging is a method that evaluates frontend, backend, and data structures to identify systemic mismatches, leveraging cross-project memory to accelerate root-cause resolution.

How do I fix UI not updating after an API call using a hypothesis-driven approach?▼

To fix UI not updating after an API call, generate diagnostic hypotheses around data-model checks and API responses, validate the root cause, and apply user-confirmed changes followed by thorough testing.

Do I need architecture docs to use a diagnostics-first debugging workflow?▼

Yes, architecture docs are required to use a diagnostics-first debugging workflow, as they provide the essential context for accurate hypothesis generation, instrumentation, and validated fixes.

What's the best way to ensure safe code changes when fixing complex bugs?▼

The best way to ensure safe code changes when fixing complex bugs is to follow a diagnostic-first process that requires explicit user confirmation before applying fixes and conducting thorough testing.

When should I not use a diagnostic-first approach for bug remediation?▼

You should not use a diagnostic-first approach for bug remediation when you lack access to the underlying code, architecture docs, or templates, as the workflow requires these to generate validated fixes.