roast-my-computer

Roast My Computer

Generate a local-only developer environment roast. Run the deterministic scanner, then write a branded classic-Macintosh-style HTML report using references/HTML_REPORT_FORMAT.md.

Operating rule

Run locally through the executing agent, using the user's filesystem. Treat memory, paths, dotfiles, source code, credentials, scan JSON, and generated reports as private. Secret values must stay redacted.

Workflow

1. Check for existing reports

Before scanning, check the stable report directory for artifacts from a previous run:

REPORT_DIR="${TMPDIR:-/tmp}/roast-my-computer"
mkdir -p "$REPORT_DIR"
ls -t "$REPORT_DIR"/computer-roast-report-*.html 2>/dev/null | head -1

On Windows use %TEMP%\roast-my-computer instead.

If a previous report exists, ask the user:

• Open the existing report — open the most recent HTML file with open / xdg-open / start. Skip scanning entirely. Done.
• Clean up and re-scan — delete all computer-roast-report-*.html and computer-roast-scan.json in the report directory, then continue to step 2.

If no previous report exists, continue directly to step 2.

2. Pick one scope

Offer only these choices unless the user already chose:

1. Project — scan the current working directory. This fits restricted environments that can only read the active repo/workspace.
2. Global — let the agent use memory/context to add the user's high-frequency folders, then scan those plus common macOS/Linux/Windows developer locations. Tell the user this is more accurate and may require approving extra filesystem access.

Use Project for "this repo", "current workspace", "safe", or permission-limited runs. Use Global for "my computer", "full roast", "most accurate", or when the user wants the agent to use memory.

3. Build roots

For Project, use the current working directory. Add explicit paths only when the user supplied them.

For Global, first use the agent's memory/context to identify likely user folders: frequent repos, workspaces, design assets, downloads, monorepos, or tool-specific config locations. Then add common defaults from references/DIRECTORY_TARGETS.md.