HugoDorne
- 10 skills
- 0 followers
- 15 hours ago last updated
- ▌ Doc · hugodorneGenerate documentation for existing code — Javadoc, OpenAPI/Swagger annotations, Architecture Decision Records (ADRs), or README sections. Use when the user asks to document a class/method/endpoint, add API docs or Swagger annotations, write an ADR for a design decision, or produce a module/package README. French triggers: "documente cette classe", "ajoute la Javadoc", "génère la doc", "écris un ADR", "annotations Swagger/OpenAPI", "rédige le README". Code examples are Java/Spring, but ADR and README generation are language-agnostic.
- ▌ Explain · hugodorneExplain how code works — purpose, an ASCII flow/structure diagram, a step-by-step walkthrough, key design decisions, and gotchas. Use whenever the user wants to understand a file, class, method, or feature they didn't write or have forgotten: "how does this work", "walk me through this", "what does this do", "explain this code/function". French triggers: "comment ça marche", "explique-moi ce code", "à quoi sert cette fonction", "explique cette classe", "détaille ce que fait ce code". Also when onboarding to an unfamiliar part of a codebase.
- ▌ Pr Hitl · hugodorne bundleReview a Bitbucket pull request *with the human in the loop* — check the PR branch out in a throwaway git worktree, open it in a new IntelliJ window, and walk through the change together step by step so the reviewer actually understands and retains the code, then optionally post the review comments. Use whenever the user gives a Bitbucket PR URL and wants to understand, learn, discuss or walk through it rather than get a verdict: "review this PR with me", "walk me through this PR", "let's look at this PR together", "explain this PR", "I want to understand this change", "open this PR in IntelliJ". French triggers: "review cette PR avec moi", "on regarde cette PR ensemble", "explique-moi cette PR", "je veux comprendre ce changement", "fais-moi un walkthrough de la PR", "ouvre cette PR dans IntelliJ". Prefer this over `pr-review` whenever the user wants to learn from the PR, be walked through it, or discuss it interactively — `pr-review` is the fast autonomous alternative. Never posts anything to Bitbucket witho
- ▌
- ▌ Pr Review · hugodorne bundleReview a Bitbucket pull request autonomously from just its URL — check the PR out in a throwaway git worktree for full file context, review the change against dev and stack conventions, and present the findings plus the exact comments that would be posted, for approval before anything reaches Bitbucket. Use whenever the user drops a Bitbucket PR link and wants it reviewed, assessed or commented on: "review this PR", "what do you think of this PR", "any problems with this PR", "can I approve this", "review and comment on this PR". French triggers: "review cette PR", "relis cette PR", "qu'est-ce que tu penses de cette PR", "y a-t-il des problèmes dans cette PR", "commente cette PR", "je peux approuver cette PR". This is the fast autonomous mode — if the user wants to be walked through the PR to *understand* it, or wants it opened in IntelliJ, use `pr-hitl` instead. Never posts anything to Bitbucket without explicit permission.
- ▌ Smart Compact · hugodorneCompact the conversation context while preserving what matters most. Use this skill whenever the user runs /smart-compact or asks to "compact", "summarize and compact", or "clean up the context". French triggers: "compacte la conversation", "résume et compacte", "nettoie le contexte", "fais un résumé de la session". It generates a structured summary of the session — what was worked on, what changed, decisions made, and what's still pending — then triggers /compact with that summary as the guiding prompt so the compacted context retains the right information for the next session.
- ▌ Version Check · hugodorne bundleCheck a project's dependencies for newer available versions and apply the ones the user chooses. Use whenever the user asks about outdated or out-of-date dependencies, available upgrades, bumping/updating libraries or packages, "what can I update", "are my deps current", or wants to refresh Maven (pom.xml) or npm (package.json) versions. French triggers: "mes dépendances sont-elles à jour", "quoi mettre à jour", "vérifie les mises à jour", "bump les versions", "dépendances obsolètes", "qu'est-ce que je peux mettre à jour". Works for Maven and Node/npm projects, including multi-module Maven builds. Reports updates grouped by risk and only edits files for the upgrades the user approves — it never bulk-upgrades silently.
- ▌
- ▌
- ▌