VasanthandClaude Opus 5.5
3942fad6cd
The skill scans a bot with subagents (never runs it) and writes HANDOVER.md, an 11-section ops guide in the operator's order: where is what, how to run, how long to wait, after the run, how to see an exception, exception list, how you will know, how to tell us, don'ts, issues seen before. Dev material (check against 12 failure classes from Tebra Auto Post, gaps with file:line, incidents) goes to HANDOVER-DEV.md. Also adds ADR-0004, glossary terms, five fixture bots and a handoff eval runner (--resume, --regrade) with results from 47 runs of the earlier 13-section version. The grader still expects that structure and must be updated before the next eval run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
32 lines
2.9 KiB
JSON
32 lines
2.9 KiB
JSON
{
|
|
"case": "h-packaged-desktop/screens",
|
|
"rep": 1,
|
|
"passed": true,
|
|
"checks": {
|
|
"HANDOVER.md written": true,
|
|
"no other file changed": true,
|
|
"bot never run": true,
|
|
"no placeholders left": true,
|
|
"13 sections in order": true,
|
|
"used subagents": true,
|
|
"every status listed": true,
|
|
"catalogue: 4+ complete rows": true,
|
|
"F1-F12 all accounted for": true,
|
|
"no code refs in ops sections": true,
|
|
"fix-before-handover has file refs": true,
|
|
"no secrets or personal data": true,
|
|
"where-to-look respects ops access": true,
|
|
"asks escalation": true,
|
|
"asks ops access": true,
|
|
"known incidents from history": true,
|
|
"display scaling rule": true,
|
|
"version check": true,
|
|
"shortcut prerequisite": true,
|
|
"silent update failure flagged": true
|
|
},
|
|
"cost_usd": 1.4194375999999997,
|
|
"subagents": 2,
|
|
"work_dir": "C:\\Users\\ec10866\\AppData\\Local\\Temp\\handoff-h-packaged-desktop-screens-2biod2mu\\project",
|
|
"reply": "I've written `HANDOVER.md` at the repo root. I only read the code and git history; I didn't run the bot, and no code was changed.\n\n| Item | Count |\n|---|---|\n| Sections | 13 (all from the template) |\n| Exceptions catalogued | 14 (E01\u2013E15; E06 isn't used) |\n| Failure classes | 10 covered, 2 not applicable (F8: no auto-rerun or watchdog; F10: no batches or locks) |\n| Fix before handover | 15 items |\n\n**Mukkiyamaana findings:**\n- **3 \"fix:\" commits um oru comment line mattum add pannudhu, code maaralai.** 125% scaling bug, launcher SSL bug, and the exe build missing the button pictures \u2014 moonum innum open. Ops rule-a \"100% scale, 1920x1080\" ah section 3-la pottiruken.\n- **Save button not found** aana, typed entry form open-aave irukkum; next line adhu mela type aagum. Double-posting risk irukku. So E08 la \"re-run pannradhukku munnaadi LedgerPro-la check pannunga\" nu pottiruken.\n- **Crash aana result file ae varaadhu**, kaaranam ops paakkura edathula edhuvum record aagadhu. Results ellam run mudiyumbodhu mattum dhaan save aagudhu.\n- **Version ops-ku engayum theriyaadhu.** Code comment \"window title\" nu sollum, aana bot-ku window ae illa.\n- `.env` (LedgerPro credentials) and oru log file git-la commit aagi irukku. Andha log-la business data irukku.\n\n**Also noticed:** Neenga \"no logs folder\" nu sonninga, aana code `logs` folder-la dhaan ezhudhudhu. Adhu illaatti rendu exe um start-laye crash aagum. \"Ops-ku logs access illa\" nu eduthukitten. `logs` folder dev/IT setup panna vendiya prerequisite-a pottiruken, *Where to look* table-la vekkala.\n\nQUESTIONS: Escalation: who does ops call for a dev issue (team or role), and how (ticket, chat channel)? | Ops access: which of the bot's places can ops open (the app's screens, the output folder, the log folder, the database)? | Unknowns: are there any statuses or exceptions whose meaning the code doesn't make clear?",
|
|
"stderr": ""
|
|
} |