Individual skill
investigate
Investigate an issue report, or analyze the constraints of a proposed change, with strict, evidence-driven diagnosis.
packages/eve-code/extension/skills/investigate/SKILL.md
Source commit d1578ec3ff6b83ee2a4816018f5d33aa80a504cd
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 5,824
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- framework Repository topic
- harness Repository topic
- javascript Repository topic
- markdown Repository topic
- typescript Repository topic
- vercel Repository topic
- sandbox Repository topic
- workflows Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Investigate
Determine unambiguously what the report means from the system's perspective. Collect the available evidence for it, such as error output, logs, and failing inputs, and check what changed recently in the affected area. Then establish whether it is real with a precise reproduction. If not, pause and report that result.
Start at the observed effect and identify the code paths directly responsible. Climb one layer at a time across call frames, processes, network hops, and persistence boundaries. Go only as wide and deep as the evidence requires.
Keep an explicit hypothesis at every branch and try to disprove it. Prefer the simplest explanation that accounts for all observed evidence. Do not jump to solutions before diagnosis.
Before proposing a change, name the fundamental constraints, including the relevant data flows and the entry points that reach the affected code paths.
## Standards
- Resolve every cited call frame and reference.
- Distinguish observations, inferences, and unknowns.