agentleFS
open-thoughtsopen-thoughts/OpenThoughts-Agent/.agents/skills/debug/SKILL.md

debug

Skill309 starsChanged 4 months agoApache-2.0View on GitHub

Debug a code bug with a structured debug log that records hypotheses, changes, and results.

191 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-discord, add-slack 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.
  • MicrosoftSkill

    add-discord

    Add Discord bot channel integration via Chat SDK.

    Also in 11 projects that use this

  • MicrosoftSkill

    add-slack

    Add Slack channel integration via Chat SDK.

    Also in 11 projects that use this

  • +10 more from microsoft

The file

Files
SKILL.md
<!-- Vendored from marin-community/marin-style v0.3.0 — do not edit; re-run `marin-style sync`. -->

Skill: Debug

Systematic debugging for code-level bugs. Keep a structured debug log so each hypothesis, the change that tests it, and its result are recorded — this keeps a long investigation from looping and makes the reasoning reviewable.

For infrastructure or operational faults, first read any operations runbook the repo provides and follow its matching section; the guardrails there (what you may and may not touch on shared infrastructure) take precedence.

Code bugs

Maintain a debug log at docs/debug-log-<task-name>.md:

# Debugging log for <task>

<goal>

## Initial status
<initial status, as reported or observed>

## <Hypothesis N>
The suspected source of the bug, or a change needed to isolate it.

## Changes to make
Which files you are altering and how.

## Results
Test results and any new hypotheses. Repeat the Hypothesis/Results cycle as needed.

## Future work
- [ ] Cleanups observed along the way

Work one hypothesis at a time: state it, make the smallest change that confirms or refutes it, record the result, then move on. When the fix lands, capture a regression test (see the write-tests skill) so the bug cannot return silently.

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.