Skip to content
Agentmart
Submit a tool

release-notes

Use this skill when asked to write versioned release notes and you need repo-specific structure, ordering, and scope filtering.

Skill by dekart-xyz

IndexedAGPL-3.0★ 436
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/dekart-xyz-release-notes

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Use this skill when asked to write versioned release notes and you need repo-specific structure, ordering, and scope filtering.

Use cases: writing, productivity, documentation, writing-editing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/release-notes

What's inside

Skill name
release-notes
Description
Use this skill when asked to write versioned release notes and you need repo-specific structure, ordering, and scope filtering.
License
AGPL-3.0
Instructions
25 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Release Notes Skill

## Trigger

Use this skill when asked to write release notes.

## Instructions

- Use `docs/release-notes-0-21-0.md` as the formatting template and section style baseline.
- Present items in this exact order:
  1. User-facing features first.
  2. Operator behavior changes second.
  3. Other changes important for admins/operators third.
  4. User-facing bug fixes fourth.
  5. Upgrade instructions last.
- Add a dedicated `Behavior Changes` section for changes that can alter existing deployment behavior or require operator action.
- Include environment variables only when they are relevant to operator action, compatibility, or upgrade safety. Do not include exhaustive variable inventories.
- Skip chore/internal-only changes that do not affect users or admins (for example CI/workflow-only changes).
- Keep language outcome-focused (what changed for users/admins), not implementation-heavy.
- Include only changes in the requested version/tag diff range.
- Use the major.minor release version in release-note copy and image tags (for example `0.23`).
- Never mention release-candidate tags or patch versions in release notes, even when an RC commit or tag defines the diff endpoint.
- Every `DEKART_LICENSE_KEY` mention must include the CTA: `[Get a key free here](https://mailchi.mp/dekart/upgrade-to-sso)`.

From dekart-xyz/dekart, AGPL-3.0.

More from dekart-xyz/dekart

Signals

Stars
436
Forks
62
Open issues
34
Last commit (this folder)
Jun 3, 2026 (4 months ago)
Last release
Oct 6, 2026 (22 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
AGPL-3.0
Repository
github.com/dekart-xyz/dekart
Website
dekart.xyz
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from dekart-xyz

Cite this page

release-notes skill. Agent Mart. https://agentmart.dev/skills/dekart-xyz-release-notes (last updated 2026-10-24)