agentsclimarketplace
Sign in

Ami release drafter

Skill AnaCataVC/amiga-ia/skills/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

Install
npx -y skills add AnaCataVC/amiga-ia --skill ami-release-drafter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 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

  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]).
    • 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):

    • 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)

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most ship operate skills give in 565 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

  • Document a rollback plan before deploymentin 41 of 779, across 22 files
  • Update the changelogin 21 of 779, across 19 files
  • Run the test suitein 20 of 779
  • Create an annotated git tagin 20 of 779
  • Clean up feature flags after full rolloutin 18 of 779, across 10 files
  • Verify deployment health after launchin 18 of 779, across 10 files
  • Test both feature flag statesin 17 of 779, across 9 files
  • Verify the working tree is cleanin 17 of 779
  • Make database migrations backward-compatiblein 16 of 779, across 8 files
  • Set up error monitoring before launchin 15 of 779, across 7 files
  • Monitor metrics at each rollout stagein 14 of 779, across 5 files
  • Create a GitHub releasein 14 of 779

Said here and by no other author read

  • Filter out minor non-functional changes
  • Draft release notes in Markdown
  • Provide English section first
  • Provide Spanish section second
  • Identify breaking changes
  • Communicate in the user's chat language

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.