Skip to content
Development
Skill

/session-report

Generate post-session summary with work performed, outcomes, and resource usage.

From plugin
plan-build-run
1847 skills18 agents70 commands

Claude Code

$ npx -y skills add SienkLogic/plan-build-run --skill session-report --agent claude-code

SKILL.md

session-report.SKILL.md
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.**

/pbr:session-report -- Post-Session Summary

**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.

Step 0 -- Immediate Output

**Before ANY tool calls**, display this banner:

+--------------------------------------------------------------+
|  PLAN-BUILD-RUN > SESSION REPORT                             |
+--------------------------------------------------------------+

Then proceed to Step 1.

Step 1: Parse Arguments

1. Parse `$ARGUMENTS` for optional flags:

  • `--since <time>` -- git log time filter (default: "8 hours ago")
  • `--save` -- write report to `.planning/reports/session-{date}.md`

2. Compute the time window for analysis

Step 2: Gather Session Data

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"

Step 3: Compute Metrics

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

Step 4: Generate Report

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}

Step 5: Optional Save

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:

  • Display only. Do not write any files.

Error Handling

  • No commits in time window: "No commits found since {since}. Try --since '24 hours ago'."
  • No STATE.md: "No .planning directory found. Run /pbr:new-project first."
  • Git not available: stop with error
Read more
@sienklogic
Ships withplan-build-run

Plan it. Build it. Run it. A Claude Code plugin for structured development with context-engineered agents.

1847 skills18 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
18
Star history of SienkLogic/plan-build-run on GitHub, a chart by star-history.com

Other skills on plan-build-run.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills10d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc11d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react1d252k
@facebook@facebookInstall Skill

Questions about session-report.

Which coding agents can use session-report?
session-report installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.