Fix a bug
with agent skills.

Start with the failing behavior. These skills cover different parts of debugging, from collecting a reproduction to checking whether a repair holds. Choose one that fits the evidence you already have.

Filter these skills by stack and access

Choose a skill

If you cannot reproduce the problem, look for diagnosis and investigation. If the failure is understood, look for a focused repair workflow. Browser testing, error recovery and final verification address different jobs; read the source note before choosing.

Follow the guided Bug hunt

Before you install

Give the agent the failing command or user journey, the expected result, the actual result and any relevant logs with secrets removed. State which files it may edit and which systems it must leave alone.

Open a listing to read its source, access labels and review evidence before copying its install command. The automated scan covers SKILL.md, not referenced files or runtime behavior. Read the review limits.

Skills for this task

12 available skills, listed A to Z. Task labels help narrow the choice; they do not establish fit for your project.

Check the result

  1. 01

    Reproduce the original failure before changing code. Record the smallest case that still fails.

  2. 02

    Test one explanation at a time, then make a focused change at the cause.

  3. 03

    Repeat the original reproduction and relevant regression tests. Report any behavior that could not be checked.