skills.rest
Aias
AiasCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dig

Conduct read-only investigations with citations anchored to source data.

Updated Nov 26, 2025
Search Tags:#debugging#investigation#evidence#traceability#root-cause#code-reading
One-click install
npx skills add https://github.com/Aias/dotfiles --skill dig-aias
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dig
Source: https://github.com/Aias/dotfiles/tree/main/agents/skills/dig
Command: npx skills add https://github.com/Aias/dotfiles --skill dig-aias

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exhaustive, read-only investigation mode to produce a verified answer with evidence anchored to source data. It ensures every claim is traceable to a specific line, commit, log entry, or data point read during the investigation.

Core Features & Use Cases

  • Read-only investigative mode that prioritizes thoroughness over speed.
  • Cross-source analysis spanning code, logs, diffs, PR histories, and external references to uncover root causes.
  • Enforces citation requirements and avoids speculative conclusions to deliver verifiable findings.
  • Useful for bug investigations, behavior explanations, and post-mortems where accuracy is crucial.

Quick Start

Begin by describing the problem, then trace the data flow and consult logs and diffs to verify each claim.

Frequently Asked Questions about dig

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

FAQPage Schema
How do I investigate a bug and trace its root cause across source code and logs?▼

Root cause investigation requires cross-referencing source code, logs, PR history, and diffs to trace behavior. This mode enforces strict evidence requirements, ensuring every finding is anchored to specific data points read during the analysis.

What is the best way to perform an evidence-backed code reading for a post-mortem?▼

Evidence-backed code reading for post-mortems involves tracing data flow and verifying claims against commits and log entries. This approach enforces citations for every claim, avoiding speculative conclusions to deliver verifiable findings.

Can I use this investigative mode to analyze external references alongside my codebase?▼

Yes, this investigative mode applies cross-source analysis spanning codebases, logs, diffs, PR histories, and external references. It ensures thoroughness by verifying each claim against multiple sources to uncover true root causes.

How do I start an exhaustive investigation when tracing unexpected application behavior?▼

Begin by describing the problem, then trace the data flow through the codebase. Consult logs and diffs to verify each claim, maintaining a read-only approach that prioritizes thoroughness and strict citation requirements over speed.

Does this investigation approach modify code or system state during analysis?▼

No, this investigation approach operates strictly in a read-only mode. It prioritizes exhaustive analysis and verifiable findings anchored to source data, enforcing no modification or open-ended speculation throughout the process.

Related Skills

Explore More Software Engineering Skills→
yu13130122297yu13130122297

scout

Identify uncertainties in research framing, datasets, metrics, and baselines.

Community
Intermediate
kirvinkirvin

post-mortem

Analyze completed work sessions to identify friction points and propose actionable improvements.

Community
Intermediate
esassocesassoc
6

csharp-test-coverage

Execute C# tests with coverlet and generate line and branch coverage reports.

Official
Intermediate
ArabelaTsoArabelaTso
142

failure-oriented-instrumentation

Instrument suspicious code regions with logging, tracing, and assertions.

Community
Intermediate