plugins/standards/skills/write-overview/SKILL.md
Content guidelines for generating overview, highlights, motivation, and journey sections.
npx skillsauth add qmu/workaholic write-overviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate structured overview content by analyzing commit history for a branch.
Run the bundled script to collect commit information:
bash ${CLAUDE_PLUGIN_ROOT}/skills/write-overview/scripts/collect-commits.sh [base-branch]
Default base branch is main.
{
"commits": [
{
"hash": "abc1234",
"subject": "Add feature X",
"body": "Detailed description of the change...",
"timestamp": "2026-01-15T10:30:00+09:00"
}
],
"count": 15,
"base_branch": "main"
}
Generate JSON with four components:
A 2-3 sentence summary capturing the branch essence:
Write in past tense. Synthesize from commit subjects.
Array of 3-5 meaningful changes:
A paragraph synthesizing the "why":
Write as narrative prose, not a list.
Two parts:
flowchart LR
subgraph Phase1[Initial Setup]
direction TB
a1[First step] --> a2[Second step]
end
subgraph Phase2[Core Work]
direction TB
b1[Third step] --> b2[Fourth step]
end
Phase1 --> Phase2
flowchart LR for horizontal timelinedirection TB inside each subgraph for vertical flowReturn JSON:
{
"overview": "2-3 sentence summary capturing the branch essence",
"highlights": [
"First meaningful change",
"Second meaningful change",
"Third meaningful change"
],
"motivation": "Paragraph synthesizing the 'why' from commit context",
"journey": {
"mermaid": "flowchart LR\n subgraph Phase1[Initial Work]\n direction TB\n a1[Step 1] --> a2[Step 2]\n end\n ...",
"summary": "50-100 word summary of the development journey"
}
}
documentation
Release note content structure and guidelines for GitHub Releases.
testing
Ship workflow - merge PR, deploy via CLAUDE.md, and verify production.
development
Generate branch-story sections 4-7 (Outcome, Historical Analysis, Concerns, Successful Development Patterns) from archived tickets and carry-over verdicts. Used by the report workflow when assembling a PR story.
business
Story writing, PR creation, and release readiness assessment for branch reporting.