Skip to content
TrustedSkillsbeta
Back to all skills

Debug With File

Checked
catlog22·vlatest·testing·MIT

Analyzes code errors from provided files to suggest fixes and pinpoint root causes for faster debugging.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add catlog22/claude-code-workflow --skill debug-with-file -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

catlog22

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned catlog22/claude-code-workflow at 07491b04ac.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
07491b04ac
Manifest
.codex/skills/debug-with-file/SKILL.md
Scanned
1 file, 580 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill, "Debug With File," enhances debugging workflows by providing an evidence-based exploration process. It records and consolidates insights during debugging sessions, corrects misunderstandings, and preserves learned information even from failed attempts. The core workflow involves exploring the error source, documenting understanding, logging analysis results, correcting hypotheses, fixing the code, and verifying the solution.

When to use it

  • When encountering a bug that requires detailed investigation and root cause analysis.
  • For complex debugging scenarios where initial assumptions might be incorrect or require refinement.
  • To maintain a documented record of the debugging process for future reference or collaboration.
  • When needing assistance in validating hypotheses and identifying potential fixes.
  • To leverage previously recorded insights from similar bugs (using ccw spec load --category debug).

Key capabilities

  • Session Management: Automatically detects existing debugging sessions and resumes them, or starts a new session if one doesn't exist.
  • Understanding Documentation: Creates and updates an understanding.md file to track the evolution of understanding during the debugging process.
  • Hypothesis Generation & Validation: Generates testable hypotheses and uses analysis to validate them.
  • Logging Instrumentation: Adds NDJSON logging instrumentation for detailed error tracking.
  • Analysis-Assisted Correction: Validates and corrects initial hypotheses based on analysis of debug logs.
  • Consolidation: Simplifies proven-wrong understanding within the understanding.md file to avoid clutter.

Example prompts

  • "Debug this bug: $BUG." (This will initiate a new debugging session for the specified bug.)
  • "Continue debugging session for bug $BUG." (Resumes an existing debugging session for the specified bug.)
  • "Analyze the debug log and update my understanding of the problem." (Triggers the analysis mode to evaluate hypotheses and correct misunderstandings.)

Tips & gotchas

  • The skill relies on a project root directory, determined by Git if available, otherwise falling back to the current working directory. Ensure your project has a .workflow/ directory in this location.
  • Running ccw spec load --category debug can provide known issues, workarounds, and root-cause notes for common bugs.