thinking-partner
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this…
Generate post-session summary with work performed, outcomes, and resource usage.
$ npx -y skills add SienkLogic/plan-build-run --skill session-report --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/session-reportContext preview
The summary Claude sees to decide when to auto-load this skill.
Generate post-session summary with work performed, outcomes, and resource usage.
name: session-report description: "Generate post-session summary with work performed, outcomes, and resource usage." allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion argument-hint: "[--since <time>] [--save]"
**STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Begin executing Step 1 immediately.**
**References:** `@references/ui-brand.md`
You are the orchestrator for `/pbr:session-report`. This read-only skill generates a summary of work performed during the current session. By default it displays the report without writing files.
**Before ANY tool calls**, display this banner:
+--------------------------------------------------------------+ | PLAN-BUILD-RUN > SESSION REPORT | +--------------------------------------------------------------+
Then proceed to Step 1.
1. Parse `$ARGUMENTS` for optional flags:
2. Compute the time window for analysis
1. Read `.planning/STATE.md` for current position (phase, plan, status) 2. Count commits in time window:
git log --oneline --since="{since}" --format="%H %s"3. Get file change stats:
git diff --stat HEAD~{commit_count}..HEAD 2>/dev/null || git diff --stat --since="{since}"4. Read SUMMARY-*.md files modified during this session:
git log --since="{since}" --diff-filter=AM --name-only --format="" -- ".planning/phases/*/SUMMARY-*.md"Extract status and key outcomes from each. 5. Check for VERIFICATION.md updates:
git log --since="{since}" --diff-filter=AM --name-only --format="" -- ".planning/phases/*/VERIFICATION.md"6. Check test results if a test command was run recently:
git log --since="{since}" --oneline --grep="test"1. **Commit breakdown**: count commits by type (feat, fix, refactor, test, docs, chore) 2. **File breakdown**: count files by directory/category 3. **Phase progress**: compare STATE.md current plan vs total plans 4. **Velocity**: commits per hour estimate
Display the report:
SESSION REPORT
==============
Session Window: {since} to now ({duration} estimate)
Current Phase: {phase_number} - {phase_name}
Current Status: {status}
WORK PERFORMED
--------------
Commits: {total_count}
feat: {feat_count}
fix: {fix_count}
refactor: {refactor_count}
test: {test_count}
other: {other_count}
Files Changed: {file_count}
Insertions: +{insertions}
Deletions: -{deletions}
PLAN PROGRESS
-------------
{For each SUMMARY written during session:}
Plan {NN}: {status} - {one-liner}
VERIFICATION
------------
{If VERIFICATION.md was updated:}
Score: {score}
Status: {status}
{Else:}
No verification updates this session.
NEXT STEPS
----------
{Based on STATE.md status, suggest the logical next command:}
- If status is "planned": /pbr:build {N}
- If status is "executing": /pbr:build {N} (continue)
- If status is "verifying": /pbr:review {N}
- If status is "complete": /pbr:milestone or /pbr:plan {N+1}If `--save` flag was provided: **CRITICAL: Create the reports directory and write the report file NOW.**
1. Create directory: `.planning/reports/` (if not exists) 2. Write report to `.planning/reports/session-{YYYY-MM-DD-HHmm}.md` 3. Display: "Report saved to {path}"
If `--save` was NOT provided:
Plan it. Build it. Run it. A Claude Code plugin for structured development with context-engineered agents.
Repo: SienkLogic/plan-build-run
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this…
Run audit, prioritize findings, auto-fix via quick tasks, test, and commit.
Review past Claude Code sessions for PBR workflow compliance and UX quality.
Run multiple phases hands-free. Chains discuss, plan, build, and verify automatically.
Manage backlog items — ideas not ready for active planning. Add, review, promote, or remove.
Start a new project. Deep questioning, research, requirements, and roadmap.