agentleFS
ahonnahonn/dotfiles/.claude/skills/investigate/SKILL.md

investigate

Skill62 starsChanged 2 months agoMITView on GitHub

Diagnose reproducible or intermittent failures by tracing evidence to a root cause and verifying a targeted fix.

129 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pair-agent, plan-devex-review and 10 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.
  • seek888Skill

    pair-agent

    Pair a remote AI agent with your browser. One command generates a setup key and prints instructions the other agent can follow to connect. Works with OpenClaw, Hermes, Codex, Cursor, or any agent that can make HTTP requests. The remote agent gets its own tab with scoped access (read+write by default, admin on request). Use when asked to "pair agent", "connect agent", "share browser", "remote browser", "let another agent use my browser", or "give browser access". (gstack) Voice triggers (speech-to-text aliases): "pair agent", "connect agent", "share my browser", "remote browser access".

    Also in 10 projects that use this

  • seek888Skill

    plan-devex-review

    Interactive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".

    Also in 13 projects that use this

  • ShreyRaviSkill

    landing-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

  • ayudaySkill

    setup-deploy

    Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".

    Also in 14 projects that use this

  • ayudaySkill

    cso

    Chief Security Officer mode. Performs OWASP Top 10 audit, STRIDE threat modeling, attack surface analysis, auth flow verification, secret detection, dependency CVE scanning, supply chain risk assessment, and data classification review. Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review".

    Also in 17 projects that use this

  • ramybarsoumSkill

    document-release

    Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped.

    Also in 18 projects that use this

  • +1 more from seek888

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 116 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use evidence to explain the failure before changing behavior.

    line 10
  2. Distinctive:

    Follow the global AGENTS.md for authorization and test mode.

    line 12
  3. Distinctive:

    Read the complete error and relevant execution path.

    line 16
  4. Distinctive:

    If reproduction is unavailable, use logs, traces, and code evidence to narrow the cause.

    line 19
  5. Distinctive:

    Use an independent opinion when a complex or high-risk diagnosis would benefit from it, or when explicitly requested.

    line 44

“Common” is measured: kept by at least 6 in 10 of the 116 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Systematic Debugging

Use evidence to explain the failure before changing behavior. Scale investigation to uncertainty and impact; a clear stack trace may need only a short trace, while intermittent failures may need instrumentation.

Follow the global AGENTS.md for authorization and test mode. Continue work already authorized by the session. Do not impose additional approval gates, a fixed retry limit, or mandatory test-first development.

Collect evidence and reproduce

  • Read the complete error and relevant execution path. Identify the expected and observed behavior.
  • Establish when the failure began and whether it depends on inputs, timing, environment, or recent changes.
  • Reproduce with the smallest relevant command, test, or manual sequence. For intermittent failures, record the conditions and frequency.
  • If reproduction is unavailable, use logs, traces, and code evidence to narrow the cause. State the remaining uncertainty; do not claim verification from inspection alone.
  • Inspect actual OS, runtime, SDK, or dependency versions when they affect the hypothesis. Do not diagnose version problems from memory.
  • For unavailable tools or external services, inspect the failure enough to choose a useful next step. Use an equivalent authorized fallback when appropriate; do not turn an unrelated tool outage into a separate repair project.

Narrow the cause

Trace the failing value or operation across boundaries. Compare working and failing cases, and vary one relevant factor at a time when practical.

PatternEvidence to seek
Race conditionTiming-dependent shared state, missing sequencing, stale async results
Null propagationThe earliest point an expected value becomes absent
State corruptionMutation, cache invalidation, stale closures, ownership violations
Integration failureContract mismatch, version skew, differing configuration
Stale cacheCached content or build artifacts that differ from the current source
Test pollutionShared state, missing cleanup, order-dependent behavior

A test passing in isolation does not prove test pollution. Compare suite execution, concurrency, environment, and timing. If order dependence is established, narrow the predecessor set to find the shared-state leak; do not fix it by reordering tests.

Test hypotheses

For each material hypothesis, identify the evidence, predict an observable result, run a focused experiment, and update the explanation from the result. Avoid changing several unrelated things and attributing success to one of them.

When experiments stop producing new information, revisit assumptions and widen the trace. A recurring symptom after a patch is evidence that the explanation or fix is incomplete: check whether the patch executed, reassess the causal chain, and preserve evidence that still holds. Do not discard valid evidence or stop at an arbitrary attempt count.

Use an independent opinion when a complex or high-risk diagnosis would benefit from it, or when explicitly requested. Verify that opinion against the code and observations. Ask the user only for missing evidence, access, or a decision that blocks further useful authorized work.

Implement and verify

Fix the demonstrated cause with a focused change. Preserve necessary error handling; distinguish a valid boundary guard from a guard that merely hides a broken invariant. Avoid unrelated refactors, and remove temporary instrumentation when it is no longer useful.

Apply the test mode chosen under global AGENTS.md. Add a regression test when that mode calls for one; test-first is optional unless explicitly selected. Run the relevant existing checks and required project checks. Broaden validation only when the change or results justify it.

Report the root cause, supporting evidence, change, checks actually performed, and material unverified behavior. If the cause remains uncertain, distinguish a mitigation or hypothesis from a confirmed fix.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.