agentleFS
Sign inStart free
tmussertmusser/ai-engineering-skills/skills/bug-capture/SKILL.md

bug-capture

Skill6 starsChanged 3 months agoMITView on GitHub

Preserve discovered bugs as BUGS.md entries.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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 when a bug is found, whether or not it is fixed in the current session.

    line 14
  2. Very specific:

    Create or update BUGS.md.

    line 26
  3. Distinctive:

    Add a bug title.

    line 27
  4. Distinctive:

    Add hypothesis and status.

    line 31
  5. Distinctive:

    Add resolution if fixed.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Bug Capture

Purpose

Preserve discovered bugs as artifacts.

When to use

Use when a bug is found, whether or not it is fixed in the current session.

Inputs

  • Observed behavior
  • Expected behavior
  • Reproduction steps
  • Affected files
  • Verification command

Workflow

  1. Create or update BUGS.md.
  2. Add a bug title.
  3. Record observed and expected behavior.
  4. Write reproduction steps.
  5. List affected files.
  6. Add hypothesis and status.
  7. Record verification command.
  8. Add resolution if fixed.

Outputs

  • BUGS.md entry with bug title, observed behavior, expected behavior, reproduction steps, affected files, hypothesis, status, verification command, and resolution if fixed

Stop conditions

  • The bug is captured well enough for another session to reproduce.
  • The issue is not a bug and should become a decision or task instead.

Anti-patterns

  • Leaving bug knowledge trapped in chat history.
  • Recording "broken" without reproduction steps.
  • Closing a bug without verification evidence.

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