debugtools / contributing
Contributing
debugtools contributions should be small, reproducible, and tied to a real debugging workflow.
Pick one surface
Start with a single tool, parser, import format, route, test, or documentation gap.
File a reproducible issue
Include affected route, steps, sample input, expected behavior, actual behavior, browser/OS, and screenshots for UI bugs.
Use local commands
Run npm install, npm run dev, focused Jest tests, npx tsc --noEmit --pretty false, and npm run build for TSX or route changes.
Keep privacy explicit
State whether the change is local-only, sends a user-requested network request, or uses optional API Workbench sync.
Open a scoped PR
Keep patches reviewable, update docs/changelog when behavior changes, and list verification commands in the PR body.