release-notes-html

Generates a self-contained HTML release-notes page from session evidence and repository state.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill release-notes-html-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-notes-html
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/packages/claude-dev-env/.agents/skills-archived/release-notes-html
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill release-notes-html-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning completed development work into a polished, product-facing release-notes page requires manually gathering evidence from commits, tests, pull requests, and approvals, then writing and designing launch copy. This Skill automates that synthesis into one valid HTML file. ## Core Features & Use Cases - Evidence-grounded content: Builds every claim from conversation history, repository files, git state, test results, and pull request data, preserving exact technical values in code elements. - Structured launch page: Produces a hero section, capability highlights, usage instructions, specifications, validation coverage, and release status with responsive, accessible design. - Acceptance audit: Verifies every factual claim against available evidence and reviews readability at desktop and narrow widths before delivery. - Use Case: After finishing a feature in a session, ask for release notes and receive a complete RELEASE_NOTES.html page a non-engineer can skim, with headings that tell the whole story. ## Quick Start Ask the assistant to build release notes HTML for the work completed in this session.

Frequently Asked Questions about release-notes-html

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create release notes from work done in a coding session?▼

Invoke the skill with a request like "build release notes for the work you've done." It gathers evidence from the conversation, repository state, tests, and commits, then writes a self-contained HTML launch page.

What sources does the release notes page use for its claims?▼

It uses only session-supported evidence: conversation history, repository files and git state, source-of-truth documents, test and CI output, approvals, and pull request or commit data. Unsupported claims are excluded.

Where is the generated HTML release notes file saved?▼

It writes to an explicit path stated in the session, or beside existing release, report, or acceptance artifacts as RELEASE_NOTES.html. The OS temporary directory is used only when no project location can be determined.

Can the release notes page be read by non-engineers?▼

Yes. The page uses plain-language headings, one-idea sentences, and bolded leads so the full story is understandable from headings alone, with exact technical values kept inside code elements.

What happens if the session lacks enough information about the feature?▼

The skill asks one concise clarification question only when the session does not contain enough information to identify the completed feature or its supporting evidence.