How do I install the Managing Entries skill?

Run npx skillmds add majiayu000/managing-entries in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Managing Entries safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Managing Entries?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Managing Entries free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Managing Entries?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Managing Entries by majiayu000 — Agent Skill

Name: Managing Entries
Rating: 4.5 (4 reviews)
Author: majiayu000

Managing Entries

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.

majiayu000 d486b38 2 files · 2.8 KB Updated Sep 9, 2026 567 repo stars

File contents

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

Type	Use When
`breaking`	User action required (API changes, removed features, renamed options)
`feature`	New capability that didn't exist before
`bugfix`	Something was broken and is now fixed (crashes, wrong output, regressions)
`change`	Modifications 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

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

---name: managing-entriesdescription: 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.--- # 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 | Type | Use When | | ---------- | --------------------------------------------------------------------------- | | `breaking` | User action required (API changes, removed features, renamed options) | | `feature` | New capability that didn't exist before | | `bugfix` | Something was broken and is now fixed (crashes, wrong output, regressions) | | `change` | Modifications 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: ```bash uvx tenzir-changelog show ``` Prefer structured output via the `--json` flag: ```bash # 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 ```bash 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: ```bash 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

Frequently asked questions