From pr-provenance-stamp
Previews the provenance receipt for the current session ledger, showing prompts, estimated spend, test results, and agent-authored line counts.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pr-provenance-stamp:provenanceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`node "${CLAUDE_SKILL_DIR}/../../pr-provenance-stamp.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/pr-provenance-stamp.js" --render`
!node "${CLAUDE_SKILL_DIR}/../../pr-provenance-stamp.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/pr-provenance-stamp.js" --render
The block above is the provenance receipt exactly as it would be stamped into a PR
body when you run gh pr create — built from the most recent session ledger the
pr-provenance-stamp hook has been recording (tool calls, test/typecheck commands
with real exit codes, and the agent-vs-human authored-line split). Prompt and spend
figures come from the transcript at PR-create time, so they may be absent in this
preview.
Briefly summarize the receipt for the user: how many tests ran and whether they are green, and the agent-authored line count or percentage. Keep it to a sentence or two and do not re-run any commands.
npx claudepluginhub karanb192/claude-code-hooks --plugin pr-provenance-stampGenerates a personal Claude Code usage & impact report from local session transcripts and git history. Useful for justifying spend, self-review, or activity check-ins.
Views, dashboards, and exports deep-work slice evidence receipts (JSON). Triggers on `/deep-receipt` and `receipt dashboard` requests. Sub-page of deep-status hub.
Generates an in-chat session report from Claude Code transcripts, showing every tool call, sub-agent delegation, and file edit with diagnostics for missed parallelism and redundant work.