New to Claude Skills? Learn how to install them →

Get Claude Skills
nexu-io on GitHub

Release Notes One-Pager

Free

Generate structured HTML release notes effortlessly.

by nexu-io84.9k stars on nexu-io/open-design
1 views
Updated Aug 10, 2026
Get this skill

Free · Opens the source repo

What Release Notes One-Pager does

The Release Notes One-Pager skill simplifies the process of creating a comprehensive release notes document in HTML format. This skill is designed for developers and project managers who need to communicate updates, fixes, and known issues in a clear and structured manner. By following a straightforward workflow, users can produce a single-page document that includes sections for highlights, added features, fixed issues, breaking changes, known issues, and upgrade notes.

To get started, users will copy a provided template HTML file into their project and customize it with relevant project details. The skill guides users through a series of steps, ensuring that each section of the release notes is properly formatted and includes the necessary information. If certain details are missing, the skill will insert explicit placeholders, such as "No summary provided" or "No additions provided," maintaining transparency about the document's contents.

The skill also emphasizes the importance of honesty in documentation. If any information is not provided by the user, the skill will not make assumptions or guesses. Instead, it will clearly indicate what information is absent, helping teams avoid miscommunication. This feature is particularly useful for teams that prioritize accuracy and clarity in their release notes.

Overall, the Release Notes One-Pager skill is ideal for software development teams looking to streamline their release documentation process. By automating the structure and formatting of release notes, this skill saves time and ensures consistency across documentation efforts.

When to use it

Use this skill when you need to generate structured release notes for software updates or project changes.

When not to use it

This skill may not be suitable if you require highly customized release notes or advanced styling beyond the provided template.

What you can build with it

Generating Release Notes for a Software Update

When a new version of your software is ready, use this skill to create clear and concise release notes that highlight changes.

Documenting Project Changes for Stakeholders

Use the skill to prepare a one-page summary of project updates for stakeholders, ensuring they are informed of new features and fixes.

Creating Consistent Release Notes Across Teams

Implement this skill across your development teams to maintain a standardized format for release notes, improving communication.

How to install Release Notes One-Pager

View source

1. Install with the skills CLI

npx skills add nexu-io/open-design/release-notes-one-pager --agent claude-code

2. Or install it manually

Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.

Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs

Inside SKILL.md

Written by nexu-io

Release Notes One-Pager Skill

Produce a single-page release notes document in HTML.

Resource map

release-notes-one-pager/
├── SKILL.md                    ← this file
├── example.html                ← quality bar and style reference
├── assets/
│   └── template.html           ← local seed file to copy to project index.html
└── references/
    ├── checklist.md            ← P0 / P1 / P2 gates
    └── layouts.md              ← local section skeletons

Do not write CSS from scratch unless the user explicitly asks for a bespoke structure.

Workflow

Step 0 — Pre-flight

  1. Read assets/template.html.
  2. Read references/layouts.md.
  3. Read active DESIGN.md and map it to the six :root variables.

Step 1 — Start from the shared seed

Copy assets/template.html to project index.html.

Update:

  • <title>
  • topnav logo text
  • topnav link labels (destinations are pre-wired to #added, #fixed, #upgrade-note)
  • topnav CTA label and href destination, or omit the topnav CTA entirely if no real destination exists
  • ensure the topnav link targets exist by adding matching section id attributes

Step 2 — Build release-note structure

Inside <main id="content">, compose this section order:

  1. Hero (Layout 1 or 2): version, date, one-sentence summary.
  2. Added (use Layout 7 log-list; section root must include id="added").
  3. Fixed (use Layout 7 log-list; section root must include id="fixed").
  4. Breaking changes (use Layout 7 log-list, or one row explicitly saying "None"; section root must include id="breaking-changes").
  5. Known issues (Layout 7 or card list; section root must include id="known-issues").
  6. Upgrade note (short steps list or explicit no-action statement; section root must include id="upgrade-note").
  7. Closing CTA strip (Layout 6).

For every CTA in the emitted HTML (topnav, hero, closing strip), replace both the visible label and the href destination with real, safe values. If no real destination is available, omit the CTA entirely—do not use a placeholder such as href="#", a misleading page-anchor, or REPLACE_WITH_REAL_URL. Hero CTAs are optional; only add them when real destinations exist.

Step 3 — Honesty rules for missing details

If the user does not provide details, do not invent them. Write explicit placeholders:

  • Summary: No summary provided.
  • Added: No additions provided
  • Fixed: No fixes provided
  • Breaking changes: None
  • Known issues: None reported
  • Upgrade note: No upgrade actions required based on provided information

If release version or date is missing, use — and label the field rather than guessing.

Step 4 — Self-check

Run references/checklist.md. Every P0 must pass.

Step 5 — Emit artifact

Wrap output as:

<artifact identifier="release-notes-one-pager" type="text/html" title="Release Notes">
<!doctype html>
<html>...</html>
</artifact>

One sentence before the artifact. Nothing after </artifact>.

Frequently asked questions about Release Notes One-Pager

Similar skills

Markdown to HTML Conversion

Efficiently convert Markdown documents to HTML.

Code Tour

Create structured walkthroughs for codebases.

Acquire Codebase Knowledge

Streamline onboarding with comprehensive codebase documentation.

Documentation & Modernization

Streamline codebase documentation and modernization planning.

Azure Resource Visualizer

Generate architecture diagrams for Azure resources.

CLAUDE.md Improver

Optimize your CLAUDE.md files for better project context.