branch-recaplisted

Takes stock of what a branch actually changed, before it gets pushed — works out the scope itself, then lays the change out group by group in one pass: files touched, what was done and why, how, and what deserves a second look, quoting code only where a remark needs it rather than reprinting the diffs. Closes on a single question set so the user steers without wading through hunks, and can then file the fixes decided along the way into the commits they belong to, via fixup and autosquash. Use it whenever someone wants to find out what happened on their own unmerged work — "relis ma branche", "on repasse sur mes commits", "vérifier ce que j'ai fait hier soir", "qu'est-ce que j'ai changé au juste sur cette branche", "fais le point avant que je pousse", "repasser sur ce que j'ai fait avant de demander une revue", "check my work before I open the MR/PR", "walk me through my changes" — including when the code was produced fast with an assistant and they no longer know what is in there, when they only name a commit
Malo-T/claude-toolbelt · ★ 2 · Code & Development · score 68

Install: claude install-skill Malo-T/claude-toolbelt

# Branch Recap Tell the user what happened on their branch, so they can settle it before pushing. The situation this exists for: the work got produced fast — often with an assistant holding the keyboard — the result works, and nobody really knows what it changed. Taking stock is the job. So the deliverable is **what was done, why, how, and what deserves a second look**, group by group, and then one question set to steer from. Not the code: the user has `git diff`, and what they lack is the account of it. Quote a few lines only where a remark is unreadable without them, and let them ask for any diff they want to see. Two failure modes to avoid. Reprinting the branch: a wall of hunks is unreadable in a terminal, and every line of it pushes the decisions further down the scroll. And chopping the account into prompts: a question between every two groups scatters the remarks across a corridor of round-trips. **One account, one question set, one round of fixes.** ## Invocation ``` /branch-recap [optional restriction] ``` Examples: - `/branch-recap` - `/branch-recap les 2 derniers commits` - `/branch-recap seulement le back` - "je voudrais repasser sur ce que j'ai fait avant d'ouvrir la MR" - "on a produit ça en deux heures, qu'est-ce qui a changé au juste avant que je pousse ?" ## Step 1 — Resolve the scope Never start reading before you know exactly what you are reading and the user has seen it. **The default is the current branch against its parent, up to their last comm