0d64d8e559
Tracked: morrowind agent (py/cfg), skills/, training-data/, research/, notes/, specs/, test-results/, metrics/, heartbeat/, briefings/, memories/, skins/, hooks/, decisions.md, OPERATIONS.md, SOUL.md Excluded: screenshots, PNGs, binaries, sessions, databases, secrets, audio cache, timmy-config/ and timmy-telemetry/ (separate repos)
7 lines
1.2 KiB
JSON
7 lines
1.2 KiB
JSON
[
|
|
{
|
|
"prompt": "Audit the timmy development loop infrastructure. Read ALL of these files and produce a detailed analysis:\n1. ~/.hermes/bin/timmy-loop.sh - the main loop runner\n2. ~/.hermes/bin/timmy-loop-prompt.md - the prompt given to each cycle\n3. ~/Timmy-Time-dashboard/.loop/state.json - current state\n4. ~/Timmy-Time-dashboard/.loop/claims.json - issue claim system\n5. List all cycle logs in ~/Timmy-Time-dashboard/.loop/logs/ and read the last 5 cycle logs fully\n6. Check for any other files in ~/Timmy-Time-dashboard/.loop/\n\nFor each cycle log, extract: how long the cycle took, what issue it worked on, whether it succeeded, what tools were called, and any errors or timeouts.\n\nProduce a detailed report covering:\n- Cycle timing analysis (min/max/avg duration, timeout rate)\n- Success/failure rate and error patterns\n- What the loop spends most time on\n- Any repeated failures or stuck patterns\n- How the claim system works and if there are stale claims\n- Prompt analysis: is it too long? unclear? missing context?\n- State management: is state.json being updated properly?\n\nPrint the full report to stdout.",
|
|
"chosen": "",
|
|
"session": "session_20260314_174009_ad8c87.json"
|
|
}
|
|
] |