Explains repository code behavior and rationale using session-read evidence and git history.
npx skills add https://github.com/blauwtje/exo --skill investigation-blauwtje
Please help me install this Agent Skill. Skill: investigation Source: https://github.com/blauwtje/exo/tree/main/skills/investigation Command: npx skills add https://github.com/blauwtje/exo --skill investigation-blauwtje
how walks the chain from entry to effect, why digs git blame, pickaxe, and pull requests for the reason behind a value, and teach explains both at the asker's level. - Confidence tiering: Every claim is marked verified, inferred, or unknown with its evidence anchor, so a guess is never acted on as fact. - History archaeology: Traces past renames, moves, and squash merges to the commit that actually introduced a value, including PR and issue discussion via gh. - Use Case: Ask why a retry cap is set to 50, and the skill traces the commit and pull request that set it, reports the incident that motivated it, and marks anything unproven as inferred or unknown. ## Quick Start Ask the investigation skill how the nightly sync in this repository works and where its batch size value actually comes from.High-intent search queries and answers about installing and using this skill.
Trace the value with git blame, git log --follow, and pickaxe (git log -S) to find the commit that introduced it, then read that commit's message and linked pull request. The newest commit on a line is often just a move, not the origin.
Read the actual files and follow the chain from entry point to effect, including config, environment, and call-site overrides. Name the concrete function, file, and line at each hop rather than relying on names or comments.
Git blame only shows the last commit that touched a line, which is often a rename or tidy-up, not the origin. Use git log --follow and pickaxe to trace back to the commit that actually set the value, then check its PR discussion.
Do not use it for finding file locations only, for how external libraries or APIs behave, for debugging unproven failures, or for deciding where architecture should change. Those belong to search, research, debug, or design workflows respectively.
A comment can be added years later by a different author than the one who set the value. Check the comment's own commit date against the value's origin commit; only the commit, PR, or issue that introduced the value records the real reason.
nguyenhungtran18Locates relevant code in repositories and returns path:line citations only.
Hawi254Verify code refactors preserve behavior and public interfaces.
htayjLocate and download third-party library source code and API documentation.
threadedstackDiagnose and fix failing integration tests from saved test output files.