investigate
Skill0 starsChanged 7 months agoNo licenceView on GitHub
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)
We split this skill into the rules it gives an agent
74 rules. 0 are common, 50 are distinctive, and 24 are very specific to this project.
0
Common
Most of the 108 edited versions we read keep these.
50
Distinctive
This author's own choices. Worth a look.
24
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 108 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Other versions123 projects use a version of this.
Word for word · 0
None found.
Edited · 21
- no-session/pstack★ 9642% same
- lucas-flatwhite/gstack-ko★ 4321% same
- CarbeneAI/Forge★ 955% same
- Samin12/skills★ 861% same
- blas1n/claude-skills★ 284% same
- HanksChen0110/skills★ 232% same
- chloropine/cgstack★ 124% same
- IyedBecheikh/bstack★ 120% same
- jpoindexter/theft-kit★ 131% same
- mahiunfiltered/claude-code-skills★ 131% same
11 more not listed
Wrote their own version · 102
- garrytan/gstack★ 138ksame name
- recharts/recharts★ 28ksame name
- gitkraken/vscode-gitlens★ 9.9ksame name
- vercel/eve★ 5.8ksame name
- rilldata/rill★ 3ksame name
- DenchHQ/DenchClaw★ 1.7ksame name
- DenchHQ/ironclaw★ 1.7ksame name
- cyrusagents/cyrus★ 868same name
- ceedaragents/cyrus★ 856same name
- rommapp/argosy-launcher★ 650same name
92 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use ios-clean, ios-fix and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Saqlain-811Skillios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
- Saqlain-811Skill
ios-fix
Autonomous iOS bug fixer. (gstack)
Also in 5 projects that use this
ShreyRaviSkilllanding-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 7 projects that use this
- ShreyRaviSkill
setup-gbrain
Set up gbrain for this coding agent: install the CLI, initialize a local PGLite or Supabase brain, register MCP, capture per-remote trust policy. One command from zero to "gbrain is running, and this agent can call it." Use when: "setup gbrain", "connect gbrain", "start gbrain", "install gbrain", "configure gbrain for this machine". (gstack)
Also in 6 projects that use this
- +2 more from Saqlain-811
- +2 more from ShreyRavi
In this repository39 other files it gives its agents.
- create-subagentSkill
- flutter-patternsSkill
- autoplanSkill
- benchmarkSkill
- browseSkill
- canarySkill
- carefulSkill
- checkpointSkill
- csoSkill
- design-consultationSkill
- design-htmlSkill
- design-reviewSkill
- design-shotgunSkill
- devex-reviewSkill
- document-releaseSkill
- freezeSkill
- guardSkill
- healthSkill
- land-and-deploySkill
- learnSkill
- office-hoursSkill
- open-gstack-browserSkill
- pair-agentSkill
- plan-ceo-reviewSkill
- plan-design-reviewSkill
- plan-devex-reviewSkill
- plan-eng-reviewSkill
- qa-onlySkill
- qaSkill
- retroSkill
- reviewSkill
- setup-browser-cookiesSkill
- setup-deploySkill
- shipSkill
- gstackSkill
- unfreezeSkill
- gstack-upgradeSkill
- maestro-testingSkill
- superpowersSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.