Session brief
Skill codecraftersautomation/claude-code/plugins/ccp/skills/session-brief
Write a human-readable summary of the current Claude session — the reasoning, decisions, and context behind the work — combined with current repo state. Use when the user asks for a "session summary", "brief", "what did we do/decide", "write up this session", or to complement /ccp:workstate before a profile switch. Writes .claude/ccp/handoff/SESSION_BRIEF.md. Explains that WORKSTATE = mechanical repo state while SESSION_BRIEF = reasoning and context.From its SKILL.md
npx -y skills add codecraftersautomation/claude-code --skill session-briefAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 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
2.0 KB, 363 tokens by cl100k_base, as published. Nobody here has run it
CCP: session-brief
Capture the thinking of this session — the part that lives in the conversation and would otherwise be lost when the user switches to another Claude profile. Where the workstate records what the repo looks like, the session brief records why it looks that way and where the reasoning was heading.
Steps
-
Summarize the session from conversation context:
- What the user set out to do and why.
- Key decisions and the reasoning/tradeoffs behind them.
- Approaches tried, what worked, what was abandoned and why.
- Open questions and things still undecided.
- Anything the next session would be surprised to learn the hard way.
-
Combine with repository state. If
.claude/ccp/handoff/WORKSTATE.mdexists, reference it; otherwise note the current branch and modified files so the narrative is grounded in real changes. (You can run/ccp:workstatefirst if you want the mechanical snapshot to cite.) -
Write
.claude/ccp/handoff/SESSION_BRIEF.mdas readable prose — sections, not a raw dump. -
Include this distinction near the top so readers use the right file for the right thing:
WORKSTATE = mechanical repo state (branch, diff, commits). SESSION_BRIEF = reasoning, decisions, and context.
Quality bar
Write for a competent stranger. The value here is the why — the decisions and dead-ends that aren't visible in the diff. Keep secrets out of the prose.
What this skill must never do
- Never switch accounts or touch credentials/OAuth/Keychain data.
- Never install plugins.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.