release-notes
Génère des notes de release HTML orientées utilisateurs finaux. Transforme les commits techniques en descriptions accessibles sans jargon.
When & Why to Use This Skill
This Claude skill automates the creation of professional, user-centric HTML release notes by analyzing Git commit history. It intelligently filters out technical noise (like refactors and chores) and translates complex developer jargon into clear, benefit-driven language. By bridging the gap between technical development and end-user communication, it ensures that product updates are accessible, engaging, and easy to understand for non-technical stakeholders.
Use Cases
- Product Update Automation: Automatically generate polished 'What's New' pages or changelogs directly from Git logs for every software release.
- Cross-Departmental Sync: Provide Customer Success and Marketing teams with jargon-free summaries of technical changes to help them communicate updates to clients.
- Sprint Review Reporting: Streamline the creation of stakeholder-ready reports that highlight user-facing improvements and bug fixes at the end of a development cycle.
- Open Source Maintenance: Maintain high-quality, readable documentation for contributors and users by automatically summarizing recent repository activity.
| name | release-notes |
|---|---|
| description | > |
| allowed-tools | [Bash, Read, Write, Grep, Glob, AskUserQuestion] |
| model | sonnet |
Release Notes Skill
Usage
/git:release-notes <branche-source> <branche-cible> [nom-release]
Si arguments manquants : AskUserQuestion pour demander.
Workflow
- Parser et valider arguments (branches source/cible)
- Collecter commits via
git log - Catégoriser par impact utilisateur
- Rédiger descriptions sans jargon
- Générer HTML dans
.claude/reports/
Catégories
| Catégorie | Icône | Mots-clés |
|---|---|---|
| Nouveautés | ⭐ | feat, ✨, 🚀 |
| Améliorations | 📈 | improve, ⚡, perf |
| Corrections | ✅ | fix, 🐛 |
| Sécurité | 🔒 | security |
Commits ignorés
refactor:,test:,chore:,ci:,docs:,style:- Commits de merge
- Mises à jour de dépendances
Règles de rédaction
- ZÉRO jargon - Pas de API, SQL, cache, endpoint, refactoring
- Bénéfice utilisateur - "L'application est plus rapide" vs "Optimisation SQL"
- Verbes d'action - Vous pouvez maintenant..., Nous avons corrigé...
- Phrases courtes - Max 1-2 phrases par item
Exemples
| Commit | Note utilisateur |
|---|---|
feat: implémenter cache Redis |
L'affichage est plus rapide |
fix: corriger validation email |
Certaines adresses email sont maintenant acceptées |
Output
{REPORT_PATH}/release_notes_{RELEASE_NAME}.html
References
- Template HTML - Structure et CSS du fichier généré
- Règles de rédaction - Exemples de transformation et conventions