skills.rest
elithrar
elithrarCOMMUNITY
Explore all skills by this author →
Website𝕏@elithrarGitHub

summarize-work

Analyze session history and git state to generate structured commit-message summaries.

190|14|Updated May 20, 2014
Search Tags:#git#code review#documentation#commit messages#session history#summarize#branch reviews
One-click install
npx skills add https://github.com/elithrar/dotfiles --skill summarize-work
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: summarize-work
Source: https://github.com/elithrar/dotfiles/tree/main/.config/opencode/skill/summarize-work
Command: npx skills add https://github.com/elithrar/dotfiles --skill summarize-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly summarize the work completed during a session to create meaningful commit messages and branch-review documentation, saving time and improving traceability.

Core Features & Use Cases

  • Analyze session history and git state to identify major changes, bug fixes, challenges, and review fixes.
  • Generate concise, structured summaries suitable for extended commit messages or PR descriptions.
  • Provide ready-to-use context for documentation and handoffs.

Quick Start

Use summarize-work to produce a summary from your current session and repository state.

Frequently Asked Questions about summarize-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a structured summary of my git commits and changes?▼

Summarize-work analyzes your session history and git state to produce structured summaries categorized into Features, Fixes, Refactors, Challenges, and Review fixes. Run it on your current branch to get a commit-message-ready summary of all work completed.

Can I use session summaries to speed up writing commit messages?▼

Yes. The Skill generates concise, structured summaries from your session work and git changes that are ready to use directly in extended commit messages, saving time on manual composition and ensuring comprehensive change documentation.

What's the best way to document a branch review before submitting a PR?▼

Use this Skill to analyze your session history and repository state, then export the categorized summary—Features, Fixes, Refactors, Challenges—as branch-review documentation suitable for PR descriptions and team handoffs.

Does this work for multi-session or sprint-level summaries?▼

The Skill summarizes work across feature branches and sprints by reading your session history and current git state. It's designed for both single-session commits and broader sprint documentation depending on the scope of history you provide.

How do I identify which changes are fixes versus refactors in my work?▼

The Skill automatically categorizes your changes by analyzing session history and git diffs, classifying them into Features, Fixes, Refactors, Challenges, and Review fixes so you can clearly communicate what changed and why.

Related Skills

Explore More Software Engineering Skills→
kivo360kivo360
1

moai-change-logger-2

Track and log Git activity with change significance audit reports.

Community
Advanced
shellicarshellicar

writing-style

Generate effect-focused commit messages, PR titles, and work item descriptions.

Community
Basic
alissonpefalissonpef

git-workflow-and-versioning

Structure git workflows with atomic commits, short-lived branches, and review-ready histories.

Community
Advanced
nmdranmdra
26

keep-a-changelog

Parse Git commit history and format CHANGELOG.md entries per Keep a Changelog standards.

Community
Intermediate