CHANGELOG generation, PR descriptions, and release documentation conventions.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Release Notes Skill
## Scope
Apply this skill when creating pull request descriptions, generating CHANGELOG entries, or documenting releases.
---
## CHANGELOG Format
The project follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format. The file `CHANGELOG.md` lives in the project root.
### Structure
```markdown
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
## [Unreleased]
### Added
- New features
### Changed
- Changes to existing functionality
### Fixed
- Bug fixes
### Removed
- Removed features
### Security
- Security-related changes
### Deprecated
- Features marked for future removal
```
### Entry Format
Each entry is a single line describing the change from the user's perspective:
```markdown
### Added
- Role-based access control with `createRole` and `assignRole` mutations
- Email verification flow with configurable token expiry
### Fixed
- Login validation no longer accepts empty password strings
```
### Rules
- Write entries from the user/consumer perspective, not the developer perspective
…
The line at the top of this page pins the label git:20260610.47ec162, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_nzuqpdxazbxtzb3m
GET https://markdownregistry.com/api/v1/resolve?ref=jvoliveiran/constellation-harness/release-notes
GET https://markdownregistry.com/api/v1/blob/3abac81b86f828b33950fc35ab6618fcf16e4784a74a12e4d8d87d3199b5e16b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
jvoliveiran/constellation-harness · plugins/constellation-stack-frontend/skills/frontend-design/SKILL.md · Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to…
jvoliveiran/constellation-harness · plugins/constellation-stack-infra/skills/oci-container-platform/SKILL.md · Running Docker containers and databases on OCI inside the Always Free tier — the AWS Lightsail equivalent built from…
jvoliveiran/constellation-harness · plugins/constellation-stack-node/skills/graphql-federation/SKILL.md · How to build a graphql federated API approach, composing a supergraph based on subgraph graphql servers
jvoliveiran/constellation-harness · plugins/constellation-stack-node/skills/graphql/SKILL.md · How to use graphql with Nestjs and Typescript on a code-first approach
jvoliveiran/constellation-harness · plugins/constellation-stack-node/skills/nestjs/SKILL.md · Most recommended practices and modules to use alongside with NestJS framework for backend development
jvoliveiran/constellation-harness · plugins/constellation-stack-node/skills/observability/SKILL.md · Logging, tracing, and monitoring standards using Winston and OpenTelemetry in a NestJS + TypeScript backend
jvoliveiran/constellation-harness · plugins/constellation-stack-node/skills/prisma-migrations/SKILL.md · Best practices for Prisma schema changes, migrations, seeding, and rollback in a NestJS + TypeScript backend
trpc-group/trpc-agent-go · examples/skilltoolactivation/skills/release-notes/SKILL.md · Use this skill when the user asks about release dates, release owners, rollout status, or launch checklist details.
kenryu42/cc-safety-net · .claude/skills/release-notes/SKILL.md · Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the…
agentic-community/mcp-gateway-registry · .claude/skills/release-notes/SKILL.md · Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a…
justxor/claude-code-pro-course · starter-kit/.claude/skills/release-notes/SKILL.md · Генерирует release notes / CHANGELOG между двумя тегами или от последнего тега. Используй, когда просят release notes…
thatrebeccarae/claude-marketing · skills/release-notes/SKILL.md · Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking…
openhands/extensions · plugins/release-notes/SKILL.md · Generate consistent, well-structured release notes from git history. Triggered on release tags following semver…
openhands/extensions · skills/release-notes/SKILL.md · Generate formatted changelogs from git history since the last release tag. Use when preparing release notes that…
databricks/unity-gateway · bench/terminal_bench/tasks/project-skill/environment/app/.claude/skills/release-notes/SKILL.md · Build release notes for this project. Use whenever someone asks for release notes or a changelog.