Agent skill

Changelog

Changelog style guide for writing RELEASE.md files. An agent skill from hegeldev/hegel-go.

MITAuto-check passedDevelopment

Install Changelog

skills CLI

$ npx skills add hegeldev/hegel-go --skill changelog -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install hegeldev/hegel-go changelog --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/changelog .claude/skills/changelog && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "changelog" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/changelog into .claude/skills/changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/changelog

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add hegeldev/hegel-go --skill changelog -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install hegeldev/hegel-go changelog --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/changelog .agents/skills/changelog && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "changelog" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/changelog into .agents/skills/changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hegeldev/hegel-go --skill changelog -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install hegeldev/hegel-go changelog --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/changelog .cursor/skills/changelog && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "changelog" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/changelog into .cursor/skills/changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/hegeldev/hegel-go.git --path .claude/skills/changelog

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add hegeldev/hegel-go --skill changelog -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install hegeldev/hegel-go changelog --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/changelog .gemini/skills/changelog && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "changelog" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/changelog into .gemini/skills/changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install hegeldev/hegel-go changelog

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add hegeldev/hegel-go --skill changelog -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/changelog .github/skills/changelog && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "changelog" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/changelog into .github/skills/changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add hegeldev/hegel-go --skill changelog -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install hegeldev/hegel-go changelog --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hegeldev/hegel-go.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/changelog .opencode/skills/changelog && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "changelog" agent skill from https://github.com/hegeldev/hegel-go/tree/main/.claude/skills/changelog into .opencode/skills/changelog/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "changelog", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: changelog
GitHub stars: 103
Token cost: ~1.4k tokens
SKILL.md length: 602 words
Files: 1
Skills in repo: 5
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Changelog style guide for writing RELEASE.md files. An agent skill from hegeldev/hegel-go.

Reviewing RELEASE.md
SKILL.md covers Choosing RELEASE_TYPE, Opening sentence pattern, Describe the user impact, not… and Length calibration, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Writing changelog entries

What it does

Changelog is an agent skill from hegeldev/hegel-go. Changelog style guide for writing RELEASE.md files. Use when creating or reviewing RELEASE.md, writing changelog entries, or preparing a PR that needs a changelog.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes. The repository describes itself as: Property-based testing for Go. The licence is MIT.

When your agent uses it

Reviewing RELEASE.md
Writing changelog entries
Preparing a PR that needs a changelog

Example prompts

“/changelog”

What it can do on your machine

Read from SKILL.md and the folder at commit 77ceb5d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- hypothesis.readthedocs.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Changelog loads about 1.4k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 602 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~1.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hegeldev/hegel-go at commit 77ceb5d, republished under its MIT licence (© hegeldev). 602 words, ~1,430 tokens.

Download SKILL.mdSave it as .claude/skills/changelog/SKILL.md (or your agent's skills folder).

name: changelog
description: Changelog style guide for writing RELEASE.md files. Use when creating or reviewing RELEASE.md, writing changelog entries, or preparing a PR that needs a changelog.

Changelog Style Guide

This guide describes the style for writing RELEASE.md files for hegel-go. The style is modeled on the Hypothesis changelog.

Choosing `RELEASE_TYPE`

hegel-go is currently zerover (0.x.y), so the usual semver mapping does not apply. While we are pre-1.0:

patch — bug fixes, internal changes, and new features / non-breaking API additions. The default choice.
minor — breaking changes only. Any change that requires users to update their code (renamed/removed APIs, changed signatures, behavior changes that could break downstream tests) is a minor bump.
major — not used while we are zerover. Reserved for the eventual 1.0 and beyond.

If you find yourself reaching for minor because the change feels "big," check whether it actually breaks any caller. A large new feature that adds API surface without removing or changing existing behavior is still a patch.

Opening sentence pattern

Every entry should open with a sentence that signals the scope and nature of the change:

Patch (fixes, improvements, new features): Start with "This patch ..."
Minor (breaking changes): Start with "This release ..." and explain migration
Tiny internal-only changes: A bare sentence is fine — "Internal refactoring." or "Clean up some internal code."

The opening verb should tell the reader what kind of change this is:

Change type	RELEASE_TYPE	Opening pattern
Bug fix	patch	`"This patch fixes ..."` or `"Fix ..."`
New feature	patch	`"This patch adds ..."`
Improvement	patch	`"This patch improves ..."` or `"This patch makes ... more ..."`
Performance	patch	`"This patch improves the performance of ..."` or `"Optimize ..."`
Deprecation	minor	`"This release deprecates ..."`
Breaking change	minor	`"This release changes ..."` (then explain migration)
Internal-only	patch	`"Internal refactoring."` / `"Refactor some internals."` / `"Clean up some internal code."`

Describe the user impact, not the implementation

Bad: "Refactored the socket handling code to use a shared connection pool."

Good: "This patch changes the way the client manages the server to run a single persistent process for the whole test run. This should improve the performance of running many hegel tests."

For bug fixes, describe the bug (what went wrong from the user's perspective), not just "fixed a bug":

Bad: "Fix bug in server crash detection."

Good: "Fix server crash detection. The client now properly detects when the hegel server process exits unexpectedly, instead of hanging indefinitely."

Show full SKILL.md (239 more words)Show less

Length calibration

Internal-only changes: 1 sentence. ("Refactor some internals.")
Simple bug fixes: 1-3 sentences. Describe the bug and what changed.
New features: 1-2 short paragraphs. Describe what it does and why it's useful.
Breaking changes / API changes: Multiple paragraphs. Include before/after code examples and migration guidance.

Don't pad entries. If a change can be described in one sentence, use one sentence.

Code examples

Include fenced code blocks for:

New API features (show usage)
Breaking changes (show before/after)
Anything where seeing the code is clearer than describing it

Don't include code blocks for bug fixes or internal changes.

References

Reference GitHub issues when relevant: ([#123](https://github.com/hegeldev/hegel-go/issues/123))
Reference previous versions when building on prior work
Reference related libraries/specs when relevant

Tone

Third person, present tense for describing behavior
Professional but conversational — be direct, not formal
Honest about uncertainty: "This should improve performance", "We expect this to...", "In some cases this may..."
It's okay to briefly explain why a change was made if the motivation isn't obvious

Things to avoid

No emojis
No bullet lists for single-topic entries (use them for multi-topic entries like API cleanups)
No commit hashes or PR numbers in the text (issue numbers are fine)
Don't describe the implementation when you can describe the effect
Don't use vague language like "various improvements" — be specific about what changed
Don't add marketing language or hype

Examples

Good patch (bug fix):

RELEASE_TYPE: patch

This patch fixes `Slices` generating duplicate elements in rare cases when the element generator had a very small output space.

Good patch (internal):

RELEASE_TYPE: patch

Internal refactoring of the protocol handling code.

Good patch (new feature):

RELEASE_TYPE: patch

This patch adds support for `HealthCheck`. A health check is a proactive error raised by Hegel when we detect your test is likely to have degraded testing power or performance. For example, `FilterTooMuch` is raised when too many test cases are filtered out by the rejection sampling of `.Filter()` or `Assume()`.

Health checks can be suppressed with the new `SuppressHealthCheck` setting.

Good minor (breaking change):

RELEASE_TYPE: minor

This release changes the signature of `RunHegelTest` to accept a `*testing.T` instead of a `testing.TB`:

\```go
// before
func RunHegelTest(t testing.TB, body func()) {}

// after
func RunHegelTest(t *testing.T, body func()) {}
\```

This will require updating your test function signatures, but should be strictly more expressive.

Files

Just SKILL.md in .claude/skills/changelog of hegeldev/hegel-go.

Open the folder on GitHubat commit 77ceb5d

Compare with similar skills

Changelog next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Changelog compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Changelog this skillhegeldev/hegel-go	103	—	~1.4k	Automated safety check: Pass	MIT	2 days ago
Simple Englishmoeru-ai/airi	50k	2 repos	~4.6k	Automated safety check: Pass	MIT	today
StarRocks Release NotesStarRocks/starrocks	12k	—	~1.9k	Automated safety check: Notes	Apache-2.0	today
Cutting A ReleaseTriliumNext/Trilium	38k	—	~3.2k	Automated safety check: Pass	AGPL-3.0	today
Mole CLI Release Flowtw93/Mole	70k	—	~2.6k	Automated safety check: Pass	GPL-3.0	today
React Router Release Notes Prepremix-run/react-router	57k	—	~1.1k	Automated safety check: Pass	MIT	yesterday

Similar skills

Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
50k GitHub starsUsed in 2 repos~4.6k tokens
DevelopmentAuto-check passed
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
12k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check: notes
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
38k GitHub stars~3.2k tokensUpdated today
DevelopmentAuto-check passed
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
70k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
57k GitHub stars~1.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Release
PrefectHQ/fastmcp
Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.
28k GitHub stars~2.9k tokensUpdated today
DevelopmentAuto-check passed

Questions about Changelog

What does Changelog do?

Changelog style guide for writing RELEASE.md files. An agent skill from hegeldev/hegel-go. Changelog is an agent skill from hegeldev/hegel-go.md files.

When should I use Changelog?

Changelog fits situations like: reviewing RELEASE.md; writing changelog entries; preparing a PR that needs a changelog.

How do I install Changelog in Claude Code?

Run `npx skills add hegeldev/hegel-go --skill changelog -a claude-code`. Or copy the skill folder (.claude/skills/changelog in hegeldev/hegel-go) into .claude/skills/changelog in your project. Claude Code loads it when a task matches its description.

How do I install Changelog in Codex?

Run `npx skills add hegeldev/hegel-go --skill changelog -a codex`. Or copy the skill folder (.claude/skills/changelog in hegeldev/hegel-go) into .agents/skills/changelog in your project. Codex loads it when a task matches its description.

Can I use Changelog in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hegeldev/hegel-go --skill changelog -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/changelog, .gemini/skills/changelog, .github/skills/changelog and .opencode/skills/changelog in your project.

What does Changelog need to run?

SKILL.md names no scripts, command-line tools or credentials: Changelog is instructions for the agent only.

Does Changelog access the network?

SKILL.md names 1 domain. As links in the text: hypothesis.readthedocs.io. This is read from the text; nothing was executed.

Is Changelog safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Changelog use?

Changelog is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Changelog use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Changelog?

Skills that share tags, products or a category with Changelog: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and Mole CLI Release Flow (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Changelog?

hegeldev (a GitHub organization) maintains it in hegeldev/hegel-go, which has 103 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.

Source: hegeldev/hegel-go on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Changelog

Install Changelog

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Changelog Style Guide

Choosing `RELEASE_TYPE`

Opening sentence pattern

Describe the user impact, not the implementation

Length calibration

Code examples

References

Tone

Things to avoid

Examples

Files

Compare with similar skills

Similar skills

Simple English

StarRocks Release Notes

Cutting A Release

Mole CLI Release Flow

React Router Release Notes Prep

Release

More from hegeldev/hegel-go

Self Review

Coverage

Go Concurrency

Align Libhegel

Questions about Changelog

Install Changelog

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Changelog Style Guide

Choosing RELEASE_TYPE

Opening sentence pattern

Describe the user impact, not the implementation

Length calibration

Code examples

References

Tone

Things to avoid

Examples

Files

Compare with similar skills

Similar skills

More from hegeldev/hegel-go

Related

Questions about Changelog

Choosing `RELEASE_TYPE`