# Ami Draft Release

> 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.

- Skill: `anacatavc/ami-draft-release` (Agent Skill)
- Install (CLI): `npx skillmds@latest add anacatavc/ami-draft-release`
- Raw SKILL.md: https://api.skillmd.com/api/skills/anacatavc/ami-draft-release/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: AnaCataVC (https://skillmd.com/u/anacatavc)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/anacatavc/ami-draft-release

---


# 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

1. **Extract Commits:**
   - Run `git fetch` to 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.

2. **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]`).
   - **USER-FACING PERSPECTIVE (NO INTERNAL REPOSITORY RULES OR JARGON):**
     Release notes are written strictly for external developers and end-users consuming the product, NOT internal AI maintainers.
     - **NEVER cite internal repository directive numbers or files** (e.g., "Rule 18", "Rule 12", "AGENTS.md guidelines", "user_rules").
     - **Translate internal governance into external product value:** Always frame improvements in terms of tangible user capabilities, performance optimizations, or system stability (e.g., instead of *"Automated Rule 18 prompt sanitization"*, write *"Prompt Hygiene & Sanitization: Purged emojis and pictographs from agent instructions to maximize token efficiency and prevent tone leakage"*).
   - Group the remaining commits based on their Conventional Commits prefix:
     - `feat:` -> Features / Nuevas Funcionalidades
     - `fix:` -> Bug Fixes / Correcciones de Errores
     - `refactor:`, `test:`, etc. -> Maintenance / Mantenimiento (include only if relevant to product stability)
   - Identify any breaking changes (`!` or `BREAKING CHANGE`).

3. **Draft the Release Notes (Bilingual):**
   - **STRICT FORMATTING CONSTRAINT:**
     You are **STRICTLY PROHIBITED** from using emojis in release titles, language separators, or section headers. Use only clean, professional semantic titles.
     - **Correct:** `# Release v4.2.0` / `# Lanzamiento v4.2.0`
     - **Forbidden:** `# [Flag] Release v4.2.0` / `# [Flag] Lanzamiento v4.2.0` / `### [Flag] English` / `### [Flag] Español`
   - Omit any section headers that do not contain actual changes.

   - **English Section Template:**
     ```markdown
     # Release [Version]
     
     ## BREAKING CHANGES
     
     ## Features
     
     ## Bug Fixes
     
     ## Maintenance
     ```
     
   - **Spanish Section Template:**
     ```markdown
     ---
     # Lanzamiento [Versión]
     
     ## CAMBIOS IMPORTANTES
     
     ## Nuevas Funcionalidades
     
     ## Correcciones de Errores
     
     ## Mantenimiento
     ```

4. **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.).