Skip to content
TrustedSkillsbeta
Back to all skills

Implementation Debugging

Checked
dylantarre·vlatest·testing·MIT

Dylantarre's implementation-debugging identifies and fixes code errors during automated test execution, streamlining development workflows.

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 dylantarre/animation-principles --skill implementation-debugging -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

dylantarre

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 dylantarre/animation-principles at 83597134ba.

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

Commit
83597134ba
Manifest
skills/12-by-problem-type/implementation-debugging/SKILL.md
Scanned
1 file, 96 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 enables AI agents to systematically identify, reproduce, and resolve errors within codebases. It focuses on analyzing stack traces, isolating root causes, and applying targeted fixes to restore functionality.

When to use it

  • You encounter runtime crashes or unexpected behavior in a deployed application.
  • A new feature fails during the integration testing phase.
  • Performance bottlenecks cause timeouts that require code-level investigation.
  • Unit tests are failing due to logic errors or edge cases not covered by initial reviews.

Key capabilities

  • Analyzes error logs and stack traces to pinpoint failure locations.
  • Isolates specific lines of code responsible for bugs.
  • Generates corrected code snippets based on identified issues.
  • Validates fixes against the original error context.

Example prompts

  • "The application crashes when processing large CSV files; analyze the memory usage logic and suggest an optimization."
  • "Here is a stack trace from production; identify the root cause and provide a patch for the calculateTotal function."
  • "My unit tests are failing on edge case inputs; debug the validation logic in UserValidator.js."

Tips & gotchas

Ensure you provide relevant context, such as error logs or specific code snippets, to help the agent accurately diagnose the issue. Complex bugs may require multiple iterations of debugging prompts to fully resolve underlying architectural flaws.