Stats
Actions
Tags
From runway
One-time scaffolding of CHANGELOG.md for projects that don't have one. Called by ship-from-backlog when CHANGELOG.md is missing — not triggered directly from conversation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/runway:bootstrap-changeloghaikuThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create CHANGELOG.md with this content:
Create CHANGELOG.md with this content:
# Changelog
User-visible changes, newest first. Follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format and [semver](https://semver.org/) versioning.
Then ask the user — in a single message, one question:
Where should the current version be tracked?
package.json— bump the"version"field on each releaseVERSIONfile — a plain text file at the repo root containing only the version string- CHANGELOG.md only — derive the current version from the latest
## [X.Y.Z]heading; no separate file is maintained
Wait for the answer, then append a ## Version tracking section to CLAUDE.md (create CLAUDE.md if it doesn't exist):
Version is tracked in \package.json` (the `"version"` field).`Version is tracked in \VERSION` (plain text file at the repo root).`Version is derived from CHANGELOG.md — the latest \## [X.Y.Z]` heading is the current version. No separate version file is maintained.`If the user picks option 2 and no VERSION file exists, create one containing 0.0.0.
Report what was created and the version tracking decision, then return to the caller.
Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub squalrus/runway --plugin runway