agentleFS
Sign inStart free
Thirumalai-Tech-DeveloperThirumalai-Tech-Developer/Kratos_Agent/skills/diagnose/SKILL.md

diagnose

Skill1 starsChanged 48 days agoMITView on GitHub

Investigate a specific bug or performance regression by reproducing it, testing ranked hypotheses, and proving the fix.

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use to-issues, edit-article and 8 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.
  • GoogleSkill

    to-issues

    Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

    Also in 53 projects that use this

  • simo97Skill

    edit-article

    The user will invoke this skill to help them edit an article.

    Also in 17 projects that use this

  • simo97Skill

    write-a-skill

    Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.

    Also in 44 projects that use this

  • AnasX7Skill

    setup-pre-commit

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.

    Also in 27 projects that use this

  • kennethkeimSkill

    ubiquitous-language

    Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

    Also in 15 projects that use this

  • AnasX7Skill

    scaffold-exercises

    Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.

    Also in 18 projects that use this

  • +4 more from simo97

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 174 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use for a concrete report such as an error, wrong result, broken interaction, or measurable slowdown.

    line 9
  2. Distinctive:

    Write a short ranked list of hypotheses and choose the cheapest observation that can distinguish them.

    line 13
  3. Very specific:

    Do not mask errors, broaden the rewrite, or claim a root cause without evidence.

    line 17

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

Diagnose a failure

Use for a concrete report such as an error, wrong result, broken interaction, or measurable slowdown.

  1. Capture the exact symptom and expected behavior. Inspect logs, recent changes, relevant code, and the environment without exposing secrets.
  2. Reproduce the failure using the least disruptive path. If it cannot be reproduced, identify what evidence is missing.
  3. Write a short ranked list of hypotheses and choose the cheapest observation that can distinguish them.
  4. Trace the failing value or control path to its cause. Do not treat a correlation or a plausible code smell as proof.
  5. Make a targeted fix, inspect nearby paths for the same cause, and gather evidence that the original symptom is resolved.

Do not mask errors, broaden the rewrite, or claim a root cause without evidence. Run regression tests only when the user asks for testing or verification. This Kratos skill retains the requested diagnose name; upstream currently calls it diagnosing-bugs.

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.

Check your setup, free