Build
Dev Tools
Rewrite a README, turn --help into examples, and explain an API error without the stack-trace fog.
How Dev Tools agents work
You put in
Rewrite a README, turn --help into examples, and explain an API error without the stack-trace fog.
Agent
Dev Tools
You get out
A prompt you can copy, a file you can download, and the steps to run it today.
Developer tools fail at the door. The README assumes a setup nobody has, --help lists forty flags with no example a person will copy, and an API error returns a blob that does not say whether you should change the request or wait. This shelf rewrites those surfaces so the next person, who might be you on Friday, can move.
README Doctor rebuilds install, run, test, and the command that proves the project works. The CLI rewriter turns a help dump into three examples and hides the flags that do not matter yet. The API explainer takes a status code and a body and says what broke, what to change, and whether a retry will do anything other than repeat the failure.
The agents quote your input. They do not invent a framework you are not using, a port that was not in the file, or a fix that requires a secret you should not paste. If the README never says how to run the tests, the rewrite says the tests are undocumented instead of guessing npm test.
Questions about Dev Tools
Will README Doctor push a commit?
No. It returns Markdown. You paste it back, trim what does not match the repo, and commit it yourself.
What if our CLI is huge?
Paste the help for one command, not the entire manual. The prompt is told to refuse a wall of flags and ask you to narrow it.
Does the API explainer call the API?
No. It reads the status and the body you paste. Strip tokens and customer data before you paste a production response.