Results for “changelog”

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

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.

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.

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

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.

Generates project documentation including README files, API docs, and changelogs by analyzing codebases and config files.

Transform technical tickets, PRDs, or changelogs into polished, user-facing release notes organized by category.

Create clear roadmap communication artifacts for internal and external stakeholders, including presentations, release notes, changelogs, and feature announcements.

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

Generates user-facing changelogs for stable releases of the Galyarder Framework, following calendar versioning and including breaking changes, highlights, improvements, fixes, and contributor attribution.

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

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

Write clear, developer-friendly documentation — READMEs, API references, code comments, and changelog entries — tailored to the audience and the project's voice. Use when the user says "write docs", "document this API", "update the README", "add code comments", "changelog entry", or "explain this for contributors".

Audits documentation health by scanning for README, changelog, API docs, ADRs, runbooks, onboarding guides, and diagrams, scoring coverage against project maturity, and recommending sub-skills to fill gaps.

Turns a GitHub pull request into a code-change explainer video with changelog, feature reveal, or refactoring walkthrough built from the diff, commits, and files.

Records architectural decisions and documentation to capture the context, constraints, and trade-offs behind codebase choices.

Produces high-quality written knowledge artifacts such as READMEs, guides, API specs, tutorials, runbooks, and wikis, with audience-appropriate structure and accuracy.

Post-ship documentation sync — updates README, CHANGELOG, AGENTS.md, ARCHITECTURE, and TODOS after a release. Ensures docs never drift from code. Run after /commit or /ship before closing a PR.

Use this skill for README, ADRs, runbooks, changelogs, decision records, operator docs. Trigger when the task involves programming work related to Documentation Adrs, production implementation, audits, debugging, strategy, or validation.

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

Define version control strategies for design files, component libraries, and design assets to enable team collaboration and consistency.

Write clear, concise, and accurate technical documentation including API references, user guides, tutorials, changelogs, and architecture docs, tailored to the target audience. Use when the user requests technical writing or provides relevant inputs for this workflow.

Generates serious, typeset documents (one-pagers, reports, letters, resumes, slides, equity reports, changelogs) with a warm parchment aesthetic, ink-blue accent, and single serif font per language.

Technical documentation specialist for API docs, tutorials, architecture docs, and developer experienceUse when "documentation, docs, readme, tutorial, api docs, guide, changelog, comments, openapi, documentation, api-docs, tutorials, readme, openapi, swagger, developer-experience, technical-writing, ml-memory" mentioned.

Escribe mensajes de commit, PRs e issues con tono humano en español rioplatense o técnico en inglés, siguiendo reglas de atomicidad, límite de 300 líneas y verificación previa de tests.

Route any website you need to visit through markdown.new by prefixing the URL. **WHEN TO USE:** - You would normally open a website link to read content (docs, blog posts, changelogs, GitHub issues, etc.) - You need a cleaner, Markdown-friendly view for copying notes or summarizing

Produces HTML-first visual design deliverables such as interactive prototypes, slide decks, motion demos, infographics, dashboards, landing pages, whitepapers, changelogs, business cards, social covers, and brand systems, with optional export to MP4, GIF, PPTX, PDF, or SVG.

Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.