skills.rest
timmo001
timmo001COMMUNITY
Explore all skills by this author →
Website𝕏@timmo001GitHub

diagnose

Guide debugging of software bugs, regressions, and performance issues.

5|Updated Jan 14, 2025
Search Tags:#workflow#performance#debugging#instrumentation#regressions#bug-finding
One-click install
npx skills add https://github.com/timmo001/dotfiles --skill diagnose-timmo001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: diagnose
Source: https://github.com/timmo001/dotfiles/tree/main/agents/.config/opencode/skills/diagnose
Command: npx skills add https://github.com/timmo001/dotfiles --skill diagnose-timmo001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a disciplined workflow for debugging complex and elusive software issues, reducing the time and effort required to identify root causes.

Core Features & Use Cases

  • Problem Diagnosis: Assists in diagnosing hard bugs, flaky tests, regressions, and performance slowdowns.
  • Workflow Guidance: Offers structured steps to build deterministic feedback loops, instrument code narrowly, and fix efficiently.
  • Use Case: Imagine a developer encountering intermittent UI failures; this Skill guides creating a reproducible environment and hypothesis ranking to locate the defect quickly.

Quick Start

Use the diagnose skill to systematically identify and troubleshoot software failures or regressions.

Frequently Asked Questions about diagnose

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

FAQPage Schema
How do I debug intermittent software bugs and regressions?▼

Debugging flaky tests and performance regressions requires creating a reproducible environment and ranking hypotheses to systematically narrow down potential defects using targeted instrumentation.

What is the best way to troubleshoot performance slowdowns in my code?▼

Troubleshooting performance slowdowns involves building deterministic feedback loops and applying narrow code instrumentation to pinpoint bottlenecks, ensuring you fix the actual defect quickly without unnecessary overhead.

How do I systematically find the root cause of flaky tests?▼

Systematically finding the root cause of flaky tests requires creating a reproducible environment, formulating ranked hypotheses about potential failures, and applying targeted instrumentation to verify each assumption.

Does this debugging methodology work for both functional defects and performance issues?▼

This debugging methodology works for both functional defects and performance issues by providing a disciplined workflow that guides repro steps and hypothesis formulation suitable for software engineers and QA specialists.

What are the limitations of using structured debugging workflows for elusive software issues?▼

Structured debugging workflows for elusive software issues operate under safety constraints by avoiding malicious code and prompt injections, requiring users to manually execute repro steps and apply instrumentation within their own environment.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
willdadywilldady
63

diagnosing-bugs

Diagnose software bugs through a structured six-phase feedback loop.

Community
Advanced
DevattomDevattom

debug

Debug code errors through analysis, reproduction, solution proposal, and multi-layer verification.

Community
Advanced
lucas-flatwhitelucas-flatwhite
43

canary

Monitor URLs for console errors, performance regressions, and page failures after deploy.

Community
Advanced