Summarizes code changes, validates staged diffs, updates documentation (docs/, README, CLAUDE.md, changelog), and creates git commits with aligned docs. Use when completing a feature or fix that requires documentation updates alongside code changes, writing commit messages, or updating changelogs and README files.
93
92%
Does it follow best practices?
Impact
95%
1.97xAverage score across 3 eval scenarios
Passed
No known issues
SESSION.md template creation and workflow gating
SESSION.md created
0%
100%
Title line present
0%
100%
Why section present
0%
100%
What changed section present
0%
100%
New concepts section present
0%
100%
Scope section present
0%
100%
Breaking/Migration section present
0%
100%
Template placeholder content
0%
100%
Workflow stopped — no commit made
100%
100%
No docs modified
100%
100%
Phase 1 analysis output: session summary and doc change plan
plan.md exists
100%
100%
Session Summary present
50%
100%
Summary ≤6 lines
100%
100%
Summary covers Why
100%
100%
Summary covers What/Scope
100%
100%
Doc Change Plan present
66%
100%
Plan includes doc path
100%
100%
Plan includes reason linked to SESSION
70%
100%
Plan includes diff evidence
40%
100%
Plan includes confidence level
0%
100%
Two commit candidates present
0%
100%
Commit candidates use conventional format
50%
100%
Phase 2 docs update, git add specificity, and conventional commit
Business code unmodified
100%
100%
Docs file updated
100%
100%
workflow-summary.md exists
100%
100%
git add uses docs/ path
0%
100%
git add includes CLAUDE.md SESSION.md
0%
100%
Conventional commit format
100%
100%
CLAUDE.md scope respected
100%
100%
No non-doc files in commit
0%
0%
Docs content relevant to SESSION
100%
100%
SESSION.md committed
0%
0%
56f4516
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.