Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

Malo-T

@malo-t source repo

5 published skills

  1. ▌
    Plugin Commands · malo-t
    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.
    0
    installs
  2. ▌
    Branch Recap · malo-t
    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
    0
    installs
  3. ▌
    Ignore Setup · malo-t bundle
    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).
    0
    installs
  4. ▌
    Audit Context · malo-t
    Measures where a project's Claude context is going before applying any of clean-context's levers. Reports what Glob discovers with and without ignore files applied, the twenty largest files in the repo and which are generated, the cumulative size of every CLAUDE.md loaded for this working directory, and how many MCP servers/tools are enabled. Then measures what past sessions really injected, per tool, command and file, from this project's own transcripts. Ranks the levers by estimated gain, each pointing at the skill that applies it. Read-only, writes nothing. Use when someone asks to measure or audit context bloat, "pourquoi mon contexte est plein", "combien pèse mon CLAUDE.md", "which of these should I clean first" before running ignore-setup blind, or when asked generally to optimize or reduce context usage. Skip for a request to actually apply a fix (ignore-setup's job) or to improve CLAUDE.md's content quality or wording (claude-md-management:claude-md-improver's job, not its size).
    0
    installs
  5. ▌
    Slack Changelog · malo-t bundle
    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
    0
    installs