← Portfolio
Software

FixPrompt

When a command fails, it tells you what went wrong in normal words.

How it works
Usage
fixprompt npm run dev, fixprompt git push, fixprompt docker compose up
Passthrough
Output streams normally. Nothing swallowed or reordered
Detect
Pattern matching on stderr and exit codes as they come in
Redact
Strips keys and tokens out before anything gets copied
Output
An explanation, plus a prompt you can paste into an assistant
A real run
[FixPrompt] Watching: node broken.js
 
node:internal/modules/cjs/loader:1424
  throw err;
  ^
 
Error: Cannot find module './config.json'
Require stack:
- /private/tmp/fpdemo/broken.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1421:15)
    at defaultResolveImpl (node:internal/modules/cjs/loader:1059:19)
    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1064:22)
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/private/tmp/fpdemo/broken.js' ]
}
 
Node.js v24.12.0
 
─────────────────────────────────────────
 
✗ The command failed.
  Exit code: 1
 
─────────────────────────────────────────
 
FixPrompt — Issue 1
 
What happened:
  Your app is trying to use a package or file that cannot be found.
  
  Your app seems to have kept running after this. That one action probably failed, but the rest may be working. It should still be fixed.
  
  Copy a prompt and paste it into Cursor, Claude, or ChatGPT to get a fix.
 
Error line:
  Error: Cannot find module './config.json'
 
[non-interactive] Run with a TTY to copy the debugging prompt.
A real run. Node throws a module error, FixPrompt catches it and says what it means in English.
What broke

The first version buffered output so it could analyse it, which meant long-running commands looked frozen. Anything with a progress bar was unusable. It streams straight through now and analyses a copy.

Links