harness-investigate

Reconstruct incident timelines into evidence-graded case files.

1|Updated May 23, 2026
One-click install
npx skills add https://github.com/baobao0303/harness --skill harness-investigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-investigate
Source: https://github.com/baobao0303/harness/tree/main/.agents/skills/harness-investigate
Command: npx skills add https://github.com/baobao0303/harness --skill harness-investigate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you investigate bugs, incidents, and unfamiliar code areas by producing an evidence-graded case file that a different engineer can resume cold.

Core Features & Use Cases

  • Evidence-graded findings: Confirms, deduces, and distinguishes hypotheses with clear criteria for what would verify or refute them.
  • Forensic investigation workflow: Guides scope establishment, evidence perimeter mapping, causality reasoning, and a clean final hand-off at diagnosis time.
  • Case-file persistence: Initializes and updates a structured investigation document, including follow-up sections across iterations.

Quick Start

Tell the agent: investigate the ticket TICKET-123 describing the failure mode in service X and include the relevant log file paths or any existing case file you already started.

Frequently Asked Questions about harness-investigate

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

FAQPage Schema
How do I perform a root cause analysis for an incident with messy logs?

Root cause analysis for an incident is performed by reconstructing events from available evidence to produce an evidence-graded case file. This workflow guides scope establishment, evidence perimeter mapping, and causality reasoning for a clean diagnosis hand-off.

What is an evidence-graded case file for debugging?

An evidence-graded case file is a structured investigation document that confirms, deduces, and distinguishes hypotheses with clear criteria. It initializes and updates findings, allowing a different engineer to resume the debugging investigation cold.

How do I trace an unfamiliar code area before making changes?

Tracing an unfamiliar code area involves forensic investigation and architecture tracing to build a mental model before changes are made. The process maps the evidence perimeter and routes to existing or new case outcomes to document findings.

Can I resume an incident investigation started by another engineer?

You can resume an incident investigation started by another engineer using the persisted case file. The structured document includes follow-up sections across iterations, ensuring a clean hand-off at diagnosis time for cold resumption.

What happens when confirmed evidence is unavailable during incident investigation?

When confirmed evidence is unavailable during incident investigation, the workflow enforces citation, delegation, and evidence-light fallbacks. This ensures hypotheses are distinguished and documented without fabricating missing causal links.