Batman report
Show where time actually went across projects, from Claude Code session transcripts — hours per project, sessions, and stuck signals (files rewritten many times, the same error hit repeatedly, long grinds with little steering). Use when the user asks "where did my week go", "am I working on the right thing", "/batman-report", or during a retro. Reads only, writes nothing.From its SKILL.md
npx -y skills add Hurleveur/batman --skill batman-reportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, as published. Nobody here has run it
Batman — report
Run it:
batman-report 7 # days back, default 7 — one week
/batman-report 1 is the evening version, the day just spent. Whatever the user
asks for in words is the argument: "yesterday" is 1, "this month" is 30. It
mirrors /batman-plan [days ahead], which faces the other way.
Bare name, no path: the plugin's bin/ is on PATH. Do not spell it
${CLAUDE_PLUGIN_ROOT}/scripts/report.sh — that variable is empty in the Bash
tool's environment and the command dies on /scripts/report.sh: No such file.
If the user runs ActivityWatch, batman-time --all adds today's real desk time
per project — transcripts only see the minutes Claude was in the room, and cap
gaps at five, so hand-testing and non-Claude work are missing from the numbers
above. Skip it silently if the command prints nothing; it is optional.
Then read it back in three lines, maximum:
- Where the time went, and whether the top project is the one that mattered.
If
WHY.mdexists in the top project, check the work against it. - The loudest stuck signal, if any — a file rewritten nine times or the same error four times means an approach that never worked and never got dropped.
- One question, not a lecture. "Was that the week you wanted?" beats a plan.
Don't run it unprompted, don't run it twice in a session, don't turn the numbers into a dashboard. It reads transcripts only — no tracking, no state, nothing written anywhere.