CtrlK
BlogDocsLog inGet started
Tessl Logo

jbvc/changelog-automation

Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

55

Quality

69%

Does it follow best practices?

Impact

—

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

SKILL.md

name:
changelog-automation
description:
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.

Changelog Automation

Patterns and tools for automating changelog generation, release notes, and version management following industry standards.

Use this skill when

  • Setting up automated changelog generation
  • Implementing conventional commits
  • Creating release note workflows
  • Standardizing commit message formats
  • Managing semantic versioning

Do not use this skill when

  • The project has no release process or versioning
  • You only need a one-time manual release note
  • Commit history is unavailable or unreliable

Instructions

  • Select a changelog format and versioning strategy.
  • Enforce commit conventions or labeling rules.
  • Configure tooling to generate and publish notes.
  • Review output for accuracy, completeness, and wording.
  • If detailed examples are required, open resources/implementation-playbook.md.

Safety

  • Avoid exposing secrets or internal-only details in release notes.

Resources

  • resources/implementation-playbook.md for detailed patterns, templates, and examples.

SKILL.md

tile.json