skills.rest
jmstar85
jmstar85COMMUNITY
Explore all skills by this author →
WebsiteGitHub

trace

Evaluate competing hypotheses to identify root causes in runtime failures.

153|12|Updated Apr 6, 2026
Search Tags:#architecture#debugging#trace#evidence#root-cause#hypotheses#causality
One-click install
npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill trace-jmstar85
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trace
Source: https://github.com/jmstar85/oh-my-githubcopilot/tree/main/.github/skills/trace
Command: npx skills add https://github.com/jmstar85/oh-my-githubcopilot --skill trace-jmstar85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evidence-driven tracing helps teams identify root causes when confronted with ambiguous or complex failures by evaluating competing hypotheses in parallel.

Core Features & Use Cases

  • Supports a structured workflow: Observation → Hypotheses → Evidence For → Evidence Against → Best Explanation → Critical Unknown → Discriminating Probe.
  • Useful for runtime bugs, performance issues, architecture postmortems, and config/orchestration investigations.
  • Generates a synthesized explanation with a discriminating probe to validate the hypothesis.

Quick Start

Trace the observed result by generating three distinct hypotheses, assign a tracer to each, and synthesize the best explanation.

Frequently Asked Questions about trace

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

FAQPage Schema
How do I identify the root cause of a runtime bug using competing hypotheses?▼

Trace causes quickly via competing hypotheses. It evaluates three hypotheses in parallel by gathering evidence for and against each, then synthesizes the best explanation with a discriminating probe to validate it.

What is the best way to structure an architecture postmortem analysis?▼

Trace causes quickly via competing hypotheses. It structures postmortem analysis deterministically: Observation, Hypotheses, Evidence For, Evidence Against, Best Explanation, Critical Unknown, Discriminating Probe.

Can I use evidence-driven tracing for performance and latency behavior investigations?▼

Trace causes quickly via competing hypotheses. Yes, evidence-driven tracing applies to latency behavior by assigning a tracer to each hypothesis to synthesize the best explanation of the issue.

How do I debug complex config and orchestration behavior failures?▼

Trace causes quickly via competing hypotheses. Debug orchestration behavior by generating three hypotheses, evaluating evidence for and against each, and identifying a critical unknown.

Does evidence-driven tracing work without integrating external debugging tools?▼

Trace causes quickly via competing hypotheses. It works without dependencies by providing a deterministic workflow preserving Observation, Hypotheses, Evidence For, Evidence Against, Best Explanation.

Related Skills

Explore More Software Engineering Skills→
oneforceoneforce
1

trace

Orchestrate parallel tracer hypotheses to identify evidence-based causal explanations.

Community
Advanced
EvolutionAPIEvolutionAPI
520

dev-trace

Generate ranked hypotheses with evidence for ambiguous engineering observations.

Official
Intermediate
marcmunoz-unomarcmunoz-uno
3

trace

Trace observed outcomes by comparing competing hypotheses with ranked evidence.

Community
Advanced
PriyanshKuniyalPriyanshKuniyal

parallel-debugging

Implements Analysis of Competing Hypotheses for complex debugging tasks.

Community
Advanced