learnings
Learnings
Final pre-commit sweep: did we learn anything in this session that the next person (or agent) working in this repo will regret not having written down?
The bar is high. Most sessions produce nothing worth adding. That's fine. Saying "nothing worth adding" is a valid — and often correct — outcome. Do not invent findings to justify the skill.
Step 1: Gather context
Run these in parallel:
git diff(unstaged) andgit diff --cached(staged) — what actually changedgit status— new files, deleted filesgit log --oneline -20— recent commit style and scope- Read
CLAUDE.mdif it exists (project root, then.claude/CLAUDE.md) - Read
README.mdif it exists
Also re-read this session's conversation: what did the user correct you on? What did you stumble over? What non-obvious thing did you discover about the codebase?
Step 2: Apply the bar
More from shpigford/skills
readme
When the user wants to create or update a README.md file for a project. Also use when the user says "write readme," "create readme," "document this project," "project documentation," or asks for help with README.md. This skill creates absurdly thorough documentation covering local setup, architecture, and deployment.
181screenshots
Generate marketing screenshots of your app using Playwright. Use when the user wants to create screenshots for Product Hunt, social media, landing pages, or documentation.
127favicon
Generate favicons from a source image
103feature-image
Generate a branded social media image announcing a new feature or update. Analyzes git history, auto-detects brand from codebase (Tailwind, CSS vars, design tokens), replicates UI elements, and captures via Playwright. Use when the user wants to create an announcement image, says 'feature image,' 'announcement graphic,' 'social image for feature,' or wants to visually announce a code change.
80issues
Interact with GitHub issues - create, list, and view issues.
78conductor-setup
Configure a Rails project to work with Conductor (parallel coding agents)
72