agentsclimarketplace

Bugfix doctor

Skill IdkwhatImD0ing/hackathonstarterkit/.agents/skill-improvement-workspace/baseline-skills/bugfix-doctor

Win your next hackathon: a battle-tested playbook plus an AI agent skill pipeline that scaffolds and ships your project.

Install
npx -y skills add IdkwhatImD0ing/hackathonstarterkit --skill bugfix-doctor

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.
  • 0 stars0 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

Systematic bug-fixing workflow for non-coders. Walks through reproduce, isolate, fix, test, and verify. Explains all errors in plain English. Use when something is broken and the user does not understand why.

SKILL.md

1.9 KB, as published. Nobody here has run it

Bugfix Doctor

Something is broken and the user does not understand why. Walk them through a systematic fix using plain English at every step.

Step 1: Reproduce

Ask the user:

  • What did you expect to happen?
  • What actually happened?
  • Can you show me the error? (screenshot, error message, or description)

If they provide an error message, translate it into plain English before doing anything else.

Step 2: Isolate

  • Identify the most likely root cause
  • Explain the cause in one sentence without jargon
  • If multiple causes are possible, list them ranked by likelihood
  • Show the user exactly which file and which section contains the problem

Step 3: Fix

  • Apply the smallest possible change that fixes the issue
  • Never refactor unrelated code during a bugfix
  • Never change more than 3 files for a single bug
  • Explain what you changed and why in plain English

Step 4: Test

  • Run the project and verify the fix
  • Walk the user through the same steps that triggered the bug
  • Confirm the bug is gone
  • Check that nothing else broke (run existing tests if available)

Step 5: Report

Return exactly these sections:

  1. Symptom: What the user saw (their words)
  2. Cause: What went wrong (plain English)
  3. Fix: What was changed (file names and a one-line summary per file)
  4. Verification: How to confirm it works
  5. Prevention: One suggestion to avoid this type of bug in the future

Rules

  • Always explain errors in plain English first, before showing code
  • Never blame the user for the bug
  • If the fix is uncertain, say so and propose a safe experiment
  • If you cannot find the cause, say so honestly and suggest next steps

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.