investigate-app

Diagnose production incidents through evidence gathering, root-cause analysis, and scored fix plans.

Updated May 3, 2026
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill investigate-app-claudfather
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate-app
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/investigate-app
Command: npx skills add https://github.com/Claudfather/clauDNA --skill investigate-app-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When production breaks—errors, outages, degraded performance—teams often guess at fixes and make things worse. This Skill enforces a disciplined SRE-style investigation workflow that finds the root cause with cited evidence before any fix is proposed. ## Core Features & Use Cases - Platform Detection & Evidence Gathering: Automatically detects Railway, Vercel, Docker, or Modal deployments, bootstraps missing CLIs, and launches parallel subagents to collect logs, deployment history, database state, and resource metrics. - Root Cause Analysis with Confidence Scoring: Presents findings in a structured table with High/Medium/Low confidence levels, each backed by specific log lines, metrics, or code references. - Scored Fix Plans & Documentation: Proposes fixes scored by Impact, Effort, and Risk, then generates investigation documents and numbered fix plans under documentation/planning/investigations/. - Use Case: Your API starts returning 500s after a deploy. Invoke the skill to pull Vercel error logs, trace the failing code path, identify the root cause with evidence, and receive a prioritized fix plan—without writing any code prematurely. ## Quick Start Ask the assistant to investigate why your production app is throwing errors or running slowly, and it will begin the evidence-driven debugging workflow.

Frequently Asked Questions about investigate-app

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

FAQPage Schema
How do I debug a production outage systematically?

Use a structured investigation workflow: understand the problem, detect the deployment platform, gather logs and metrics in parallel, then perform root-cause analysis before proposing fixes. This skill enforces that order with a hard gate preventing fixes until evidence gathering completes.

How to gather logs from Vercel, Railway, or Modal for debugging?

The skill auto-detects your platform and runs the right commands: `vercel logs --level error --since 1h` for Vercel, `railway logs --lines 200 --json` for Railway, and `modal app logs <app-name> --timestamps` for Modal. Missing CLIs are bootstrapped automatically.

Does this skill work with Docker or database-backed apps?

Yes. It detects Docker via docker-compose files and Dockerfiles, and checks database state for Neon (via psql with the discovered connection URL) and Snowflake (via snowsql), including connection pool exhaustion and long-running queries.

What happens if multiple fix attempts fail during debugging?

After three or more failed fix attempts, the workflow stops and escalates. Repeated failures signal an architectural problem rather than a wrong hypothesis, so the skill prompts a discussion with the user instead of further guess-and-check attempts.

Does the investigation skill apply fixes automatically?

No. It produces plans, not code. Every fix is scored by impact, effort, and risk, and the user must explicitly select which fixes to plan. The skill never builds, branches, or creates pull requests.