agentsclimarketplace

Bugfix and verify

Skill wchen02/cursor-agent-learning/.cursor/skills/bugfix-and-verify

A hands-on project to learn Cursor’s agent customization: rules, skills, subagents, commands, hooks, and AGENTS.md. Everything is set up with examples and docs so you can try things and tweak them.

Install
npx -y skills add wchen02/cursor-agent-learning --skill bugfix-and-verify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Fixes bugs or test failures using debugger → fix → verify. Use when the user reports an error, test failure, or unexpected behavior and wants a fix confirmed.

SKILL.md

1.4 KB, as published. Nobody here has run it

Bugfix and Verify Framework

This skill runs a bugfix workflow: debug, fix, then verify.

Steps

  1. Debug

    • Invoke the debugger subagent with:
      • The error message, stack trace, or failing test output (from the user or from the conversation), and
      • The relevant file(s) or area of the codebase if known.
    • Capture the debugger’s output: root cause, location, suggested fix, and how to confirm the fix.

  2. Fix

    • Apply the fix (or a minimal variant). Prefer the debugger’s suggestion unless it’s incomplete or wrong; then extend or correct as needed.
    • Make the smallest change that addresses the root cause; avoid refactors unless the user asked for them.

  3. Verify

    • Invoke the verifier subagent to confirm:
      • The original error or test failure is resolved.
      • Related behavior still works (e.g. run the test suite or the steps that previously failed).
    • Report: fixed vs still broken; if broken, summarize what the verifier found.

Notes

  • If the user only wants a diagnosis, stop after step 1 and present the debugger’s report.
  • If the user says “skip verification,” do steps 1–2 only and note that verification was skipped.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.