agentleFS
Sign inStart free
LikeMindsCommunityLikeMindsCommunity/agentic-workflow-backend/.claude/skills/diagnose-bug/SKILL.md

diagnose-bug

Skill0 starsChanged 3 months agoLicence not identifiedView on GitHub

Validate one or more bug reports and, for each real defect, diagnose the root cause and propose a fix as a PENDING row in the client's approval sheet (outputs/{client}/approval_sheet.md) — validate-only, never editing source or committing. Handles a single bug, a batch (with cross-fix interaction analysis), or "sheet" mode over existing rows. Use when a bug is reported and you want it triaged and a fix proposed for review. Also supports a KB target (target=kb): instead of source code, it analyses a knowledge base against a user's complaint about a deliverable it produced and proposes amendments to that KB for review — used by the kb-feedback pipeline. Triggers: "diagnose this bug", "diagnose-bug", "is this a real bug and what is the fix", "triage these bugs for {client}".

8 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use to-spec.

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

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

32 rules. 0 are common, 18 are distinctive, and 14 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 18

    Distinctive

    This author's own choices. Worth a look.

  • 14

    Very specific

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

The licence could not be identified — 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 8 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.

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