Malo-T
UserA belt of unrelated Claude Code plugins: guided branch review, context hygiene, and session status in the terminal tab or by ear.
Categories
Indexed Skills (5)
branch-review
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
ignore-setup
Set up a project so Claude stops discovering lockfiles, generated code, minified assets and binaries on every search — a managed .ignore, the Glob setting that makes Glob obey it, and a short read-deny list for secrets. Use when someone asks for a .claudeignore, asks to exclude files from the context, says Claude wastes time reading generated or vendored files, says searches return too much noise, or wants a project configured right after /init ("ajoute un .claudeignore", "exclure des fichiers du contexte", "nettoyer le contexte du projet"). Skip for a one-off permission tweak like "allow npm commands" (that is update-config) and for cutting permission prompts (that is fewer-permission-prompts).
branch-recap
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
slack-changelog
Turns what changed in a release into a Slack changelog a non-technical audience can read: filtered to what they would actually notice, one bullet per idea, plain language, no code vocabulary. Works out the scope itself across however many repositories sit in the working directory (a project can span several independent repos released together), separates what is visible to someone outside engineering from what isn't, groups the visible part by functional theme rather than by repo, picks an emoji per idea from a reference table, and closes on a single question round to adjust theme, bullets, closing line or target channel before handing over the final text. It never posts on its own. Use it when someone wants to announce a release to people outside engineering: "écris le changelog Slack pour cette release", "prépare le message pour annoncer les dernières nouveautés", "on doit poster ce qui a changé pour les équipes business", "draft the Slack update for this release", "what should we tell the rest of the compa
plugin-commands
Commands for validating, testing, iterating on, and releasing plugins in this marketplace (claude-toolbelt) — plugin validate, watcher-parity check, eval, --plugin-dir dev loop, plugin tag. Use when validating a plugin before pushing, running skill evals, developing a plugin without touching the installed cache, or tagging a release.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.