rmyndharis/antigravity-skills

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.

First seen Jan 24, 2026

Installation

$ npx skills add rmyndharis/antigravity-skills --skill changelog-automation

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rmyndharis/antigravity-skills · top by installs.

npx skills add rmyndharis/antigravity-skills

Browse all from rmyndharis/antigravity-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1.5K
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents antigravity

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,274 B
  • docs SUMMARY.md 226 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 16 installs

SKILL.md

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.