agentleFS
Sign inStart free
SatanshuMishraSatanshuMishra/interphase/skills/bug/SKILL.md

bug

Skill1 starsChanged 43 days agoApache-2.0View on GitHub

Use when existing behaviour is wrong and the user wants the cause found or the problem pinned down before anything is changed, such as "X does Y instead of Z", "X stopped working", "determine the cause" or "why does X".

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use init and release.

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.
  • MicrosoftSkill

    init

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ${CLAUDE_PLUGIN_ROOT}/core/phases.md in full before any other action.

    line 10
  2. Distinctive:

    If phase 2 classifies the request as a different pathway, say so.

    line 13
  3. Very specific:

    If this conversation was summarized or cleared during this run, re-read docs/specs/<slug>.record.json, docs/specs/<slug>.decisions.md and …

    line 14

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

Pathway: bug.

  1. The request is $ARGUMENTS, or the user's latest request when this skill started automatically.
  2. Read ${CLAUDE_PLUGIN_ROOT}/core/phases.md in full before any other action. Follow it with this pathway.
  3. The playbook is ${CLAUDE_PLUGIN_ROOT}/core/pathways/bug.md.
  4. The spec template is ${CLAUDE_PLUGIN_ROOT}/core/templates/spec-bug.md.
  5. If phase 2 classifies the request as a different pathway, say so. Then invoke the Skill tool with that pathway's skill instead.
  6. If this conversation was summarized or cleared during this run, re-read docs/specs/<slug>.record.json, docs/specs/<slug>.decisions.md and ${CLAUDE_PLUGIN_ROOT}/core/phases.md before acting.

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