Our review
Generates weekly or monthly structured summaries of work sessions from activity logs, retrospectives, and learnings.
Strengths
- Automates the creation of periodic reports
- Consolidates data from multiple sources (logs, retrospectives, commits)
- Provides consistent templates for summaries
- Supports historical summaries for past periods
Limitations
- Requires a specific project structure and existing log files
- Limited to weekly or monthly periodicity
- Output quality depends on completeness of source data
Use when you need a consolidated overview of completed work, decisions, and learnings for a given week or month.
Do not use for real-time updates or when you only need a quick, informal recap without structured documentation.
Security analysis
SafeThe skill uses standard bash commands (grep, find, git log, git commit) to gather data and commit generated summaries. There are no destructive operations, exfiltration, obfuscation, or network exploitation. The git commit is part of the intended workflow and does not pose a security risk.
No concerns found
Examples
/summary weekly/summary monthly/summary monthly 2026-01name: summary description: Generates weekly or monthly session summaries from retrospectives and activity logs. argument-hint: "[weekly|monthly]" user-invocable: true
Summary - Session Summaries
Generate weekly or monthly summaries from retrospectives, learnings, and activity logs.
Usage
/summary weekly # Generate current week summary
/summary monthly # Generate current month summary
/summary weekly 2026-01 # Generate for specific week/month
Output: $PROJECT_ROOT/docs/summaries/YYYY-MM-weekN.md or YYYY-MM.md
Instructions
Language Setting
Check
LANGUAGEindocs/current.md. Ifth, translate output perreferences/language-guide.md. Seereferences/bash-helpers.mdfor detection snippet.
1. Determine Period
Parse arguments:
weekly→ current week (Mon-Sun)monthly→ current month- Optional date parameter for historical summaries
export TZ='Asia/Bangkok'
YEAR=$(date '+%Y')
MONTH=$(date '+%m')
WEEK=$(date '+%V')
2. Gather Data
export TZ='Asia/Bangkok'
# Activity log entries for the period
grep "^$YEAR-$MONTH" docs/logs/activity.log
# Retrospectives for the period
find docs/retrospective/$YEAR-$MONTH -name "*.md" -type f | sort
# Learnings for the period
find docs/learnings/$YEAR-$MONTH -name "*.md" -type f | sort
# Git commits for the period
git log --oneline --since="[start-date]" --until="[end-date]"
# Knowledge base updates
git log --oneline --since="[start-date]" --until="[end-date]" -- docs/knowledge-base/
3. Analyze and Generate
Read each retrospective/learning file and extract:
- Task descriptions
- Types (feature, bugfix, refactor, etc.)
- Key decisions
- Open items (unchecked checkboxes)
4. Create Summary File
Use the template below.
5. Commit
git add docs/summaries/
git commit -m "docs: [weekly|monthly] summary for [period]"
Weekly Template
# Week [N] Summary ([start-date] - [end-date])
## Overview
| Metric | Value |
|--------|-------|
| Sessions | [count] |
| Issues Closed | [count] |
| PRs Merged | [count] |
| Learnings Captured | [count] |
## Sessions
| Date | Task | Type | Status | Issue |
|------|------|------|--------|-------|
| MM-DD | [task description] | feat/fix/refactor | completed/pending | #N |
## Key Accomplishments
- [accomplishment 1]
- [accomplishment 2]
## Learnings Captured
- `docs/learnings/[path]` - [title]
## Knowledge Distilled
- `docs/knowledge-base/[topic].md` - [title]
## Decisions Made
| Decision | Context | Rationale |
|----------|---------|-----------|
| [decision] | [context] | [rationale] |
## Open Items
- [ ] [carried over items from retrospectives]
## Next Week Focus
- [suggested focus areas based on open items]
Monthly Template
# [Month Year] Summary
## Overview
| Metric | Value |
|--------|-------|
| Total Sessions | [count] |
| Issues Closed | [count] |
| PRs Merged | [count] |
| Learnings | [count] |
| Knowledge Base Updates | [count] |
## Weekly Breakdown
| Week | Sessions | Key Focus |
|------|----------|-----------|
| W1 | [count] | [focus] |
| W2 | [count] | [focus] |
| W3 | [count] | [focus] |
| W4 | [count] | [focus] |
## Top Accomplishments
1. [accomplishment]
2. [accomplishment]
3. [accomplishment]
## Patterns & Trends
- [observed pattern in work]
- [recurring themes]
## Open Items Carried Over
- [ ] [items still pending]
## Next Month Priorities
- [priority 1]
- [priority 2]
Related Commands
| Command | Purpose |
|---------|---------|
| /td | Create retrospective (data source) |
| /mem | Capture learnings (data source) |
| /consolidate | Consolidate auto-captured files |
| /summary | Generate summaries (you are here) |
API Documentation Generator
Documentation
Automatically generates OpenAPI/Swagger API documentation.
Technical Writer
Documentation
Writes clear technical documentation following top style guides.
Pivot Decision Framework
Documentation
Documents a strategic pivot or persevere decision with evidence, analysis, and rationale. Use when evaluating whether to change direction on a product, feature, or strategy based on market feedback.