Generates and validates a transient what's-new fragment from change entries.
npx skills add https://github.com/friedbotstudio/baseline --skill whatsnew
Please help me install this Agent Skill. Skill: whatsnew Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/whatsnew Command: npx skills add https://github.com/friedbotstudio/baseline --skill whatsnew
Creates a safe handoff for “what’s new” messaging when the main context already knows the change but the final destination is decided later. It avoids premature changelog writes and keeps release-note generation separate from semantic-release.
Ask the whatsnew skill to generate a fragment from your prepared change entries and save it under the project's gitignored whatsnew state path.
High-intent search queries and answers about installing and using this skill.
To generate release notes without editing CHANGELOG.md, create a transient what's-new fragment from your change entries. This skill validates the structure and saves it to a gitignored state path for downstream publishing later.
Keepachangelog categories structure changelog entries into Added, Changed, Deprecated, Removed, Fixed, and Security updates. This skill enforces these specific categories when building your release-note fragments to ensure standardized documentation.
You route release-note fragments by configuring project.json. This skill supports optional routing resolution from project.json, allowing a site page, release body, or docs page to consume the generated fragment later.
Yes, you can use this approach with semantic-release workflows. This skill keeps release-note generation separate from semantic-release by creating a temporary buffer for your changes, avoiding premature changelog writes during automated deployments.
The whatsnew skill validates slugs, entry structure, and optional boolean highlights before writing a transient fragment. It enforces safe slug formatting and deterministic file output under the .claude/state/whatsnew directory.
Use a transient release-note fragment when the final destination for your changes is decided later. This approach works well for feature launches, bug fix batches, or docs updates where you need a temporary buffer without touching CHANGELOG.md.
microsoftAutomate Azure deployments with AZD, AZCLI, Bicep, or Terraform after validation.
ThalesGroupInspect and patch GitHub Pages docs publishing workflows.
rodmena-limitedCreate, configure, and manage Claude Code Skills with templates and tools.
Unique-AGUpdate CHANGELOG.md and pyproject.toml versions from commit history.
