investigate▌
garrytan/gstack · updated Apr 22, 2026
Debugging workflow with an explicit rule: no fixes until the root cause is understood. The flow is investigate, analyze, hypothesize, then implement.
Debugging workflow with an explicit rule: no fixes until the root cause is understood. The flow is investigate, analyze, hypothesize, then implement. Imported from investigate/SKILL.md in garrytan/gstack.
Ratings
4.5★★★★★26 reviews- ★★★★★Diya Flores· Dec 8, 2024
investigate fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Noah Flores· Nov 27, 2024
We added investigate from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Amelia Singh· Oct 18, 2024
Solid pick for teams standardizing on skills: investigate is focused, and the summary matches what you get after install.
- ★★★★★Alexander Verma· Sep 25, 2024
I recommend investigate for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Rahul Santra· Sep 9, 2024
Solid pick for teams standardizing on skills: investigate is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Aug 28, 2024
We added investigate from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Jin Khanna· Aug 16, 2024
investigate reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Sakshi Patil· Jul 19, 2024
investigate fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Aarav Okafor· Jul 15, 2024
investigate has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Jin Agarwal· Jul 7, 2024
Registry listing for investigate matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 26