Results for “keep-a-changelog”

Generates a concise bullet-point summary of branch changes for a pull request description, grouping related commits by theme and verifying details against actual files.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Archives a completed change in the OpenSpec workflow, checking artifact and task completion, assessing spec sync, and moving the change directory.

Archives a completed change in the OpenSpec workflow, checking artifact and task completion, assessing spec sync, and moving the change directory to the archive.

Records daily activities, progress, decisions, and learnings in structured chronological markdown files.

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Track code changes with structured JSON records, an enforced state machine, and a session handoff format for AI continuity.

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

Summarizes daily development progress into project-local and global diary files, then syncs them to Notion and Obsidian.

Update GSD to latest version with changelog display

Composite skill — configure a fresh or under-configured repo for the release-branch workflow in one pass. Creates the `release` branch on origin, seeds `CHANGELOG.md` (Keep-a-Changelog format), drops in `.claude/dep-sweep-config.json` + `.claude/branch-hygiene-config.json` + a `release-cadence.md` standard stub, opens a `chore/repo-bootstrap` PR to main. Use instead of manually setting these up before the first `/pr-to-release` — without this, none of the release-branch composites can fire. Idempotent: skips any artifact that already exists. Replaces ad-hoc "set up the new repo" scripts.