cf-warm
SolidCatch up after absence — summarize git history for a specific user. Use when a user returns after time away from a project and needs to understand what happened — e.g. "warm up", "catch me up", "what happened while I was away", "what did I work on", "summarize recent changes", "what changed since I left", "warm up the project".
Install
Quality Score: 82/100
Skill Content
Details
- Author
- dinhanhthi
- Repository
- dinhanhthi/coding-friend
- Created
- 6 months ago
- Last Updated
- yesterday
- Language
- TypeScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
cf-remember
Save project knowledge to docs/memory for AI recall (unlike $cf-learn, which writes educational notes for the human). TRIGGER — "remember this", "save this to memory", "document what we did", "capture this decision", "write this down", "note this", "record this convention"; after a non-obvious bug fix → bugs/, an architecture decision → decisions/, a new convention → conventions/, a feature flow or gotcha → features/. SKIP — trivial fixes, simple config changes, or educational exchanges (use $cf-learn).
cf-scan
Scan the project and populate memory (architecture, conventions, stack, features). Triggers: "scan the project", "scan the codebase", "bootstrap memory", "populate memory", "analyze the project". Token-heavy — always warn before proceeding.
cf-teach
Personal teacher skill — after any task, explains what happened in a conversational, storytelling way (like a sharp friend over coffee). Covers: approach taken, alternatives rejected, how parts connect, tools used, tradeoffs, mistakes made, pitfalls to watch, expert observations, and transferable lessons. Unlike $cf-learn (concise structured reference notes), this creates a narrative deep-dive for the human to truly understand what happened and why.