/cf-warm
Manual onlyHigh>2.5K tokens injected into promptCatch up after absence — summarize git history for a specific user.
Context footprint: ⚡⚡⚡ (high) — what does this mean?
The /cf-warm skill helps you catch up after being away from a project. It summarizes your recent commits and everything the team did since your last commit, grouped by topic/area.
Usage
/cf-warm [--user <name>] [--n-commits <N>]
Arguments
| Flag | Description | Default |
|---|---|---|
--user <name> | Git author name to look up | Auto-detected from git config user.name |
--n-commits <N> | Number of your own commits to summarize | 10 |
What It Does
- Validates git repo — Stops if not inside a git repository
- Resolves user — Auto-detects from
git config user.nameor uses--user - Dry run — Counts commits before processing to warn about large volumes
- Gathers your commits — Fetches your last N commits (messages only, no diffs)
- Gathers team commits — Fetches all other commits since your last shown commit
- Clusters by topic — Groups team commits by topic/area using AI analysis
- Writes report — Saves to
docs/warm/warm-YYYY-MM-DD.mdand shows a terminal summary - Indexes in memory — Stores the report in the memory system for future recall
Examples
# Auto-detect user, show last 10 commits
/cf-warm
# Look up a specific user
/cf-warm --user "John Smith"
# Show more of your own history
/cf-warm --n-commits 10
# Combine flags
/cf-warm --user "Jane" --n-commits 3
When to Use
- Returning from vacation — Catch up on what happened while you were away
- Context switching — Re-orient yourself when switching back to a project
- Onboarding — Get a quick overview of recent activity when joining a team
- Monday morning — Start the week knowing what changed over the weekend
Report Structure
The generated report includes:
- Your Recent Work — Summary of your last N commits, grouped by feature/fix
- What the Team Did — All other commits grouped by topic (e.g., "Frontend", "API", "Infrastructure")
- Quick Orientation — The most impactful changes you should be aware of
Safety
- Dry run first — Always counts commits before fetching to warn about large volumes
- Messages only — Uses commit messages and descriptions, not diffs (unless a message is too vague)
- Safety cap — Maximum 200 team commits to keep the report manageable
Custom Guide
Extend with .coding-friend/skills/cf-warm-custom/SKILL.md:
## Before
<!-- Run before the warm-up starts -->
## Rules
<!-- Additional rules during warm-up -->
## After
<!-- Run after warm-up completes -->