Results for “keep-a-changelog”

Turn a weekly changelog markdown into a branded square video with animated UI mockups, voiceover, and captions.

Generate user-facing App Store release notes by collecting and summarizing user-impacting changes from git history since the last tag.

Manages semantic versioning and changelog documentation for Flutter projects, defining a structured process for recording additions, changes, and removals across backend and mobile releases.

Analyzes git commit history and generates structured changelogs categorized by change type.

Update ElevenLabs agent skills from a merged weekly changelog, then open a pull request.

Generates a single unified changelog from git history, written in plain language for the whole company, defaulting to Slovak and comparing the release branch against develop for unreleased changes.

Transforms technical git commits into polished, user-friendly changelogs by analyzing commit history, categorizing changes, and generating customer-ready release notes.

Write changelogs and release notes that users actually read, with guidance on categorization, user-facing language, visuals, and distribution.

Generate consistent, auditable release notes from Conventional Commits, compute semantic version bumps, and enforce commit format linting.

Update Pythinker Code CLI user documentation after meaningful code changes that affect product behavior or user experience.

Generates the stable Galyarder Framework release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.

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

Drafts a changelog entry from local git history between two refs, matching the project's existing changelog format, and writes it to a draft file.

Generate changelog generator operations. Auto-activating skill for Technical Documentation. Triggers on: changelog generator, changelog generator Part of the Technical Documentation skill category. Use when working with changelog generator functionality. Trigger with phrases like "changelog generator", "changelog generator", "changelog".

Stop re-litigating decisions you already made. Keep a decision record where each entry captures the decision, the context that forced it, the options you weighed, why you chose, and when to revisit, one entry at a time, in plain searchable markdown you can grep later. Trigger on "log this decision", "why did we choose X", "write a decision record", "record why we're doing this", "what did we decide about", or any moment a real call gets made and would otherwise be forgotten.

Maintains a product repo's canonical docs structure (CLAUDE.md, progress.txt, docs/product+system+design-system, context/) as single source of truth, and keeps the log.md session history separate from the progress.txt state snapshot. Trigger after feature completion, before git push, on architecture changes, at session end, or explicit "update docs"/"sync documentation" requests. Skip for trivial changes (<10 LOC, no logic/schema/UI changes).

Generates and maintains project documentation: Google-style docstrings, README, architecture docs, and ADRs, with a mandatory post-task review gate to keep docs current.