agentleFS
Sign inStart free
ldaytonldayton/Dippy/.claude/skills/debug/SKILL.md

debug

Skill243 starsChanged 8 months agoMITView on GitHub

Debug incorrect Dippy approval or block behavior

192 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

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 175 edited versions we read keep these.

  • 5

    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. Distinctive:

    Search the codebase to find the relevant handler or pattern

    line 17
  2. Distinctive:

    Write a failing test FIRST in the appropriate test file

    line 18
  3. Very specific:

    Run just test and verify the test fails as expected

    line 19
  4. Very specific:

    Run just test until the test passes

    line 21
  5. Distinctive:

    ONLY modify files directly related to the bug

    line 34
  6. Distinctive:

    Do NOT refactor or "improve" unrelated code

    line 36
  7. Distinctive:

    Do NOT create a git commit or PR

    line 37

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

Debug a Dippy issue based on user-provided context.

The user will provide:

  • The command that was incorrectly approved or blocked
  • Expected vs actual behavior
  • Any relevant error messages or logs

Process

  1. Understand the bug from the provided context
  2. Search the codebase to find the relevant handler or pattern
  3. Write a failing test FIRST in the appropriate test file
  4. Run just test and verify the test fails as expected
  5. Fix the bug in the handler or pattern
  6. Run just test until the test passes

Finish

When tests pass:

uv run ruff check --fix && uv run ruff format

just check MUST pass before you're done.

Restrictions

  • ONLY modify files directly related to the bug
  • Make minimal, targeted fixes
  • Do NOT refactor or "improve" unrelated code
  • Do NOT create a git commit or PR

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