agentleFS
manastalukdarmanastalukdar/ai-devstudio/skills/debug-session/SKILL.md

debug-session

Skill1 starsChanged 7 months agoMITView on GitHub

Document debugging sessions with hypothesis tracking and knowledge base

6 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Create structured debug logs in .claude/debugging/

    line 12

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

I'll create structured documentation for your debugging session to build a knowledge base and track your investigation process.

Based on session management patterns:

  • Create structured debug logs in .claude/debugging/
  • Hypothesis tracking with test results
  • Solution documentation
  • Timeline of investigation
  • Knowledge base building for future reference

Arguments: $ARGUMENTS - session name or issue description


Token Optimization

Expected range: 150–1,200 tokens (initial), 50 tokens (session update)

Caching: Caches current debug session in .claude/cache/debug-session/current.json for 7 days.

Early exit: Returns immediately for session updates, skipping full re-analysis.

Patterns used: Grep-before-Read, early exit, caching, progressive disclosure

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.