Ami release drafter
Must be triggered before publishing any GitHub release. Analyzes git commits to automatically draft comprehensive bilingual release notes (English and Spanish) grouped by feature, bug fix, and maintenance.From its SKILL.md
npx -y skills add AnaCataVC/amiga-ia --skill ami-release-drafterAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.5 KB, 565 tokens by cl100k_base, as published. Nobody here has run it
Skill: Release Drafter
Act as a Technical Writer and Product Manager. Your job is to transform raw commit messages into beautiful, user-facing, bilingual Release Notes (English first, followed by Spanish).
Workflow
-
Extract Commits:
- Run
git fetchto ensure the local repository has all the latest commits and tags from the remote. - Run
git log <last-tag>..HEAD --pretty=format:"%s"to get the raw commit messages.
- Run
-
Categorize and Filter (Product-Centric):
- Focus on Core Product Value: Release notes MUST focus exclusively on primary product capabilities, core features, and user-facing code enhancements.
- Filter Minor/Secondary Edits: Actively exclude or omit minor non-functional changes such as pure documentation updates (
docs:), cosmetic edits to product showcase/landing pages (e.g.,index.html,landing.html), internal developer scripts, or release pipeline chores (chore:,bump version...,[skip ci]). - Group the remaining commits based on their Conventional Commits prefix:
feat:-> 🚀 Features / Nuevas Funcionalidadesfix:-> 🐛 Bug Fixes / Correcciones de Erroresrefactor:,test:, etc. -> 🛠️ Maintenance / Mantenimiento (include only if relevant to product stability)
- Identify any breaking changes (
!orBREAKING CHANGE).
-
Draft the Release Notes (Bilingual):
- Format the notes cleanly using Markdown.
- English Section:
-
Release [Version]
-
🚀 Features
-
🐛 Bug Fixes
-
🛠️ Maintenance
- (If applicable) ## ⚠️ BREAKING CHANGES
-
- Spanish Section:
-
Lanzamiento [Versión]
-
🚀 Nuevas Funcionalidades
-
🐛 Correcciones de Errores
-
🛠️ Mantenimiento
- (If applicable) ## ⚠️ CAMBIOS IMPORTANTES (BREAKING CHANGES)
-
-
Output:
- Present the drafted markdown to the user or orchestrator agent for final review.
- Do NOT create the GitHub release yourself unless explicitly told to do so. Just provide the draft.
Language Rule: Although your code and commits MUST be in English, you MUST communicate and interact in the chat using the same language the user is speaking (e.g., Spanish, French, etc.).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.