home / skills / willsigmon / sigstack / final-3-skills-for-today

final-3-skills-for-today skill

safe

/plugins/app-dev/skills/final-3-skills-for-today

This skill generates a comprehensive session wrap-up detailing git activity, achievements, metrics, and next steps to improve ship readiness.

npx playbooks add skill willsigmon/sigstack --skill final-3-skills-for-today

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

682 B

---
name: Session Summary Generator
description: Generate comprehensive session summary for Leavn work - commits, metrics, achievements, remaining work, ship readiness
allowed-tools: Bash, Read, Write
---

# Session Summary Generator

Create session wrap-up:

1. **Git stats**:
   ```bash
   git log --oneline --since="today"
   git diff --shortstat {start-commit}
   ```

2. **Count achievements**:
   - Files modified
   - Lines added/deleted
   - Bugs fixed
   - Features completed

3. **Create summary doc**:
   - SESSION_SUMMARY.md
   - Commits list
   - Metrics
   - Achievements
   - Next steps
   - Ship readiness

Use when: Session ending, need summary, planning next work

Overview

This skill generates a concise, structured session wrap-up for Leavn work. It turns git activity and development metrics into a clear SESSION_SUMMARY.md covering commits, metrics, achievements, remaining work, and ship readiness. It helps hand off context and plan next steps at the end of each coding session.

How this skill works

It inspects recent git history and diffs to extract commits, files changed, and lines added or deleted. It aggregates achievements like bug fixes and completed features from commit messages and tracked tasks. Finally it composes a SESSION_SUMMARY.md with a commits list, numeric metrics, highlighted achievements, proposed next steps, and a ship-readiness assessment.

When to use it

At the end of a focused coding session
Before leaving work to hand off context
When you need a one-page status for stakeholders
Prior to planning the next session or sprint
When preparing a release readiness check

Best practices

Run git commands before creating the summary to capture complete session activity
Use clear, imperative commit messages to improve automatic categorization
Tag feature-complete commits to highlight completed features
Quantify metrics (files changed, lines added/deleted) for objective progress tracking
Include an explicit ‘next steps’ list and owner for handoff clarity

Example use cases

Daily wrap-up for a developer working on Leavn features
Sprint demo preparation to show what shipped and what remains
Bug triage summary showing which fixes landed during the session
On-call or handover note to transfer context to another engineer
Release readiness snapshot summarizing ship blockers and pass/fail items

FAQ

What git data does the skill use?

It uses recent git log entries and git diff stats to extract commit lists, files modified, and lines added or deleted.

How does it determine achievements and remaining work?

Achievements are inferred from commit messages and tracked task markers; remaining work is drawn from open issues, TODOs in code, or incomplete items you list for the session.