agentleFS
gabrielSantosLimagabrielSantosLima/harness/skills/release-summary/SKILL.md

Release summary

Skill1 starsChanged 8 days agoMITView on GitHub

Write a short, non-technical summary of the latest release, asking the user for the language first. Use when the user asks for a release message, release notes, or a summary of what changed recently.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 10 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a short, user-facing message about the latest release.

    line 8
  2. Distinctive:

    Ask with a single-selection question containing exactly these options:

    line 13
  3. Distinctive:

    Ask every time, even when the conversation is already in one of those languages.

    line 19
  4. Distinctive:

    Never infer the language from context.

    line 20
  5. Distinctive:

    If your agent has a dedicated question tool, use it.

    line 22
  6. Very specific:

    If the range is empty, use git log --oneline <previous-tag>..<latest-tag>.

    line 34
  7. Distinctive:

    Keep only what the user can notice or do.

    line 42
  8. Distinctive:

    Never invent features that are not in the commits.

    line 46
  9. Very specific:

    Start with a bold title: What changed (en), O que mudou (pt-BR) or Que cambio (es).

    line 50
  10. Distinctive:

    Avoid technical vocabulary: API, refactor, agent, job, commit, dependency, retry, payload, migration, CI.

    line 54
  11. Distinctive:

    No file names, commit hashes, branch names or version numbers unless the user asks for them.

    line 56
  12. Distinctive:

    No emoji, no extra headings, no closing paragraph.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Release summary

Create a short, user-facing message about the latest release. The readers are end users, not developers.

1. Ask the language

Ask with a single-selection question containing exactly these options:

  1. Portuguese (Brazil) - pt-BR
  2. English - en
  3. Spanish - es

Ask every time, even when the conversation is already in one of those languages. Never infer the language from context.

If your agent has a dedicated question tool, use it; otherwise ask in plain text and wait.

2. Collect the release scope

Run:

git describe --tags --abbrev=0
git log --oneline <latest-tag>..HEAD

If the range is empty, use git log --oneline <previous-tag>..<latest-tag>. Ignore merge commits and chore(release) commits. If both ranges are empty, say there is nothing new to summarize and stop.

3. Translate commits into user-facing changes

  • Group related commits into one bullet. For example, several sync fixes become one "more reliable sync" bullet.
  • Keep only what the user can notice or do.
  • Drop everything internal: refactors, dependency bumps, CI, tests, tooling, migrations, file names, internal identifiers.
  • Fixes without a visible outcome become one "stability fixes" bullet.
  • Never invent features that are not in the commits.

4. Write the message

  • Start with a bold title: What changed (en), O que mudou (pt-BR) or Que cambio (es).
  • 4 to 7 bullets, one line each, ordered by user impact.
  • Plain, friendly language and short sentences.
  • Avoid technical vocabulary: API, refactor, agent, job, commit, dependency, retry, payload, migration, CI.
  • No file names, commit hashes, branch names or version numbers unless the user asks for them.
  • No emoji, no extra headings, no closing paragraph.
  • Output only the message, in the chosen language.

Examples

English:

**What changed**

- You can now sync your data with another device nearby, with no internet.
- Log today's reading right from the home screen in a few taps.
- Scanning is more accurate because it uses both the photo and the text.
- If a scan takes too long, a cancel button appears.

Portuguese (Brazil):

**O que mudou**

- Agora da para sincronizar seus dados com outro aparelho por proximidade, sem internet.
- Registre a leitura de hoje direto da tela inicial, em poucos toques.
- A leitura ficou mais precisa, usando a foto e o texto juntos.
- Se a leitura demorar, aparece um botao para cancelar.

Spanish:

**Que cambio**

- Ahora puedes sincronizar tus datos con otro dispositivo cercano, sin internet.
- Registra la lectura de hoy desde la pantalla de inicio en pocos toques.
- La lectura es mas precisa porque usa la foto y el texto juntos.
- Si la lectura tarda demasiado, aparece un boton para cancelar.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.