AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Release Notes

skill-jakesterns-agent-skills-release-notes · by jakesterns

Produces release notes and changelog entries from commits, pull requests, or diffs with clear user impact and upgrade guidance.

↗ Repository
— No reviews yet
0 installs
16 views
0.0% view→install

Install

$ agentstack add skill-jakesterns-agent-skills-release-notes

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Release Notes? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Release Notes

Use this skill when drafting release notes, changelog entries, upgrade notes, or release summaries.

Inputs

  • Commit log, pull request list, diff, issue list, or milestone notes
  • Target audience: users, developers, operators, or internal stakeholders
  • Version number, release date, and compatibility constraints if known

Steps

  1. Group changes by user impact: Added, Changed, Fixed, Security, Deprecated, Removed, Performance, Documentation.
  2. Translate implementation details into outcomes without hiding important technical changes.
  3. Identify breaking changes, migration steps, config changes, and operational actions.
  4. Call out security fixes without exposing exploit details.
  5. Remove duplicates and merge related items.
  6. Keep known issues and follow-up work separate from shipped changes.

Output

Return:

  • Release summary
  • Categorized changelog
  • Upgrade or migration notes
  • Known issues
  • Verification or rollout notes when useful

Guidelines

  • Be accurate about what shipped.
  • Avoid vague phrases like "various improvements."
  • Preserve version and date details exactly when provided.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills