S Skillteca
Receber por email
Explorar Categorias Coleções Newsletter
← Voltar para o catálogo

changelog-generator

Documentos Autor: mohitagw15856

Converte logs do git, listas de commits ou notas de lançamento em um changelog polido e voltado para o usuário. Ideal para criar notas de lançamento ou entradas CHANGELOG.md, gerando uma seção estruturada com cabeçalho de versão, mudanças categorizadas e notas de migração.

991estrelas
Atualizado há 4 meses
Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add mohitagw15856/pm-claude-skills

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/changelog-generator/svg)](https://www.skillteca.com.br/skills/changelog-generator)
#ai #git

Skills relacionadas

Ver todas de Documentos →

pdf

153.1k

Use esta skill para qualquer operação com arquivos PDF, incluindo leitura, extração de texto/tabelas, combinação, divisão, rotação de páginas, adição de marcas d'água, criação, preenchimento de formulários, criptografia/descriptografia, extração de imagens e OCR para torná-los pesquisáveis.

Documentos #ocr #pdf por anthropics

theme-factory

153.1k

Kit de ferramentas para estilizar artefatos com um tema. Ele oferece 10 temas predefinidos com cores/fontes, aplicáveis a vários artefatos como slides, documentos ou páginas HTML, ou permite gerar novos temas na hora.

Documentos por anthropics

pptx

153.1k

Use esta skill para qualquer tarefa que envolva arquivos .pptx, incluindo criar, editar, ler, extrair texto, combinar ou dividir apresentações.

Documentos #ai #pptx por anthropics

canvas-design

153.1k 1

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Documentos #pdf por anthropics

Alerta por categoria

Receba novas skills de Documentos toda segunda

1 email curto, só com as skills novas de Documentos. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Changelog Generator Skill

Converts raw git commits, a diff summary, or developer release notes into a polished changelog entry — categorised, user-facing, and following Keep a Changelog conventions.

Required Inputs

Ask for these if not provided:

  • Commits or release notes (paste git log --oneline, raw commit messages, or a description of what changed)
  • Version number (e.g. 2.4.0, v1.0.0-beta.2)
  • Release date (or "today")
  • Audience (developers using an API / end users of a product / internal team — affects language)
  • Any breaking changes (flag these explicitly if known)
  • Previous version behaviour (optional — paste the previous changelog entry or describe what is changing; needed for accurate "Changed" entries)
  • Scope (whole product / specific package or module — e.g. "payments SDK only", "iOS app", "all services")

Output Format

Follow Keep a Changelog format:

[X.Y.Z] — YYYY-MM-DD

Breaking Changes ⚠️

[Only include if there are breaking changes]

  • [Breaking change]: [What changed and what it breaks]
  • Migration required: [Specific action the user must take]

Added

  • [New feature or capability, written from the user's perspective]
  • [Another addition]

Changed

  • [Changed behaviour — what it did before vs. what it does now]
  • [Performance improvement with measurable impact if known]

Fixed

  • [Bug fixed — describe what was broken, not the fix implementation]
  • [Another fix]

Deprecated

  • [Deprecated thing] — use [replacement] instead. Will be removed in [version].

Removed

  • [Removed thing] — was deprecated in [version]

Security

  • [Security fix — describe the vulnerability class, not exploit details]
Skill guidance — do not include the following section in the delivered changelog:

Formatting Rules Applied

Language: Write for the reader, not the committer. "Add dark mode support" not "implement ThemeProvider with dark palette variant".

Breaking changes: Always call these out first with ⚠️. Include a migration path.

Bug fixes: Describe what was broken, not what was changed. "Fix crash when user has no profile picture" not "null-check avatar URL before rendering".

Granularity: Group related commits into one line. Don't list every micro-commit separately.

Tone: Active voice, imperative mood. "Add", "Fix", "Remove" — not "Added", "Fixed", "Removed".

Empty sections: Omit any section with no entries. Don't include empty ### Fixed blocks.

Quality Checks

  • [ ] Breaking changes are at the top with migration instructions
  • [ ] All entries are user-facing language (no internal variable names or implementation details)
  • [ ] Related commits are grouped into single entries (not listed individually)
  • [ ] Version and date header is correct
  • [ ] Empty sections are omitted
  • [ ] No entries start with past-tense verbs (no "Added", "Fixed", "Removed" — use "Add", "Fix", "Remove")
  • [ ] Every breaking change entry includes a specific migration action (not just "update your code")

Usage Examples

  • "Write a changelog for version [X]" + [paste commits]
  • "Generate release notes from these commits"
  • "Turn this git log into a CHANGELOG entry"
  • "Write the CHANGELOG.md update for this release"
  • "What changed in this release?" + [paste commit list]
Compartilhar X LinkedIn