Stats
Actions
Tags
From codeforerunner
Generate a Keep-a-Changelog entry from git history since the last release tag. Use when the user wants to write a CHANGELOG entry or document what changed in a release.
How this skill is triggered — by the user, by Claude, or both
Slash command
/codeforerunner:forerunner-changelogThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Produces a Keep-a-Changelog–style entry for changes since the last release tag. Does not require a full scan — operates on git log and diff output.
Produces a Keep-a-Changelog–style entry for changes since the last release tag. Does not require a full scan — operates on git log and diff output.
User asks to: write the changelog, generate a changelog entry, document the release, write what changed since vX.Y.Z.
git log v<last-tag>...HEAD --oneline outputgit diff v<last-tag>...HEAD --stat outputCHANGELOG.md for format referenceRun forerunner generate --prompt-only changelog — outputs the assembled prompt bundle to stdout. Read this output and execute the documentation task it describes.
Without CLI, get the prompt from:
src/codeforerunner/prompts/tasks/changelog.mdsrc/codeforerunner/prompts/system/base.mdA formatted ## [X.Y.Z] — YYYY-MM-DD section with ### Added, ### Changed, ### Fixed, ### Removed subsections. Infer the version from the tag pattern if not specified. Suitable for direct insertion into CHANGELOG.md.
npx claudepluginhub derek-palmer/codeforerunner --plugin codeforerunnerFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.