browser4-fix-bug

Fix build, test, and runtime errors through a compile-test-fix verification loop.

1.1k|151|Updated Mar 12, 2018
One-click install
npx skills add https://github.com/platonai/Browser4 --skill browser4-fix-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser4-fix-bug
Source: https://github.com/platonai/Browser4/tree/main/skills/browser4-fix-bug
Command: npx skills add https://github.com/platonai/Browser4 --skill browser4-fix-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a build fails, a test breaks, or a script crashes, developers often guess at fixes and make things worse. This Skill enforces a disciplined error-driven loop: reproduce the failure, read the exact error, make the smallest possible edit, and re-verify until the build or test passes.

Core Features & Use Cases

  • Error-Driven Fix Loop: Reproduce failures with Maven, tsc, Python, or Bash compile commands, then read only the failing lines before editing.
  • Minimal Safe Edits: Use targeted replace, regex, line-range edits, and revert operations so every change is small and reversible.
  • LSP Diagnostics Integration: Prefer language server diagnostics over full builds for faster error detection in Kotlin, TS/JS, and Python files.
  • Use Case: A Maven compile fails in the browser4-seo plugin with an unresolved reference at line 42. The Skill reads the surrounding lines, applies a one-line fix, reruns the compile, and reports the root cause with verification output.

Quick Start

Ask the agent to fix the failing build or test by reproducing the error, reading the faulty lines, applying the smallest edit, and re-running the verification command until it passes.

Frequently Asked Questions about browser4-fix-bug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a Maven compile error in a Kotlin project?

Run mvn compile on the failing module to reproduce the error, then read only the lines around the reported line number. Apply the smallest possible edit with a string replace or line-range edit, and rerun the same compile command to verify the fix.

How to debug a failing test without reading the whole file?

Run the specific test class with Maven, note the failing line from the stack trace, and read only a small window of lines around it. This keeps context focused and prevents edits to code you have not inspected.

Can LSP diagnostics replace running a full build?

For TypeScript, JavaScript, and Python, language server diagnostics return structured errors with line numbers faster than a full build. Use diagnostics as a pre-check when a language server is installed, then confirm with the real compile or test command.

What should I do when a code fix makes the build worse?

Revert the edit to restore the pre-edit snapshot, then retry with a smaller or different change. If five attempts fail, stop and report the exact error and attempted fixes instead of continuing to degrade the code.

Why make only one edit per verification cycle?

Batching multiple edits makes it impossible to know which change fixed or broke the build. One edit per verify cycle keeps every change attributable, so you always know exactly which fix worked.