OpenParable
Skip to content
← Back to skills

Managing Entries

Productivity
managing-entries

Managing Entries is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Create and manage changelog entries. Use when adding changelog entries, finishing features or bugfixes, documenting changes, writing release notes, working in changelog/ directories, wrapping up commits and PRs, or cutting a release.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/documents/managing-entries/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/managing-entries, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Changelog and Release Notes Management

This skill helps you create and manage changelog entries and release notes using the tenzir-changelog framework.

When to Use

  • After completing a feature, bugfix, or breaking change
  • When the user asks to create a changelog entry
  • When working on PR descriptions that reference changelog items
  • When validating existing changelog entries
  • When viewing or exporting release notes

Entry Types

TypeUse When
breakingUser action required (API changes, removed features, renamed options)
featureNew capability that didn't exist before
bugfixSomething was broken and is now fixed (crashes, wrong output, regressions)
changeModifications to existing functionality (improvements, refactoring, tweaks)

Use Cases

Add an Entry

Use the /changelog:add slash command.

Show Entries

Show unreleased entries in table format:

uvx tenzir-changelog show

Prefer structured output via the --json flag:

# Show detailed metadata for a specific entry.
uvx tenzir-changelog show --json 1

# Export as JSON.
uvx tenzir-changelog show --json

# Show a specific release.
uvx tenzir-changelog show --json v1.0.0

Validate

uvx tenzir-changelog validate

Checks entry structure, required fields, and manifest consistency. Reports missing metadata, duplicate IDs, and config drift.

Preview Release Notes

Preview release notes without modifying files:

uvx tenzir-changelog release notes --json v1.0.0

Best Practices

  1. One entry per logical change - Don't combine unrelated changes
  2. Link PRs - Always include PR numbers for traceability
  3. Breaking changes - Clearly explain migration steps in the body
  4. Preview first - Always preview releases before committing
  5. Validate in CI - Automate validation to enforce metadata completeness