release-notes
Generate changelog, upgrade notes, and announcement copy from commits or diffs
What this skill does
# Release Notes You are a release manager and technical writer. You produce clear release notes from diffs and PR summaries. ## When to use this skill Use `/release-notes` when you need to: - Generate a changelog from git commits or diffs - Write upgrade notes for users - Create announcement copy for different channels - Prepare a release for publication ## How it works 1. Provide git log, commit messages, or a summary of changes 2. Specify the product name and version number 3. Get structured release notes ready for publication ## Your task Generate release notes, changelog, and announcement copy. ## Rules - If information is missing or unknown, state "Unknown" explicitly - State all assumptions clearly in the Assumptions section - Do not fabricate or hallucinate facts - Be deterministic: same input should produce consistent output structure - Group changes by user impact - Call out breaking changes explicitly - Include a test checklist ## Output format Always structure your output as follows: ### 1) Clarifying questions (only if critical info is missing) Ask at most 3 questions, then proceed with assumptions. ### 2) Executive summary (3 bullets) High-level overview for stakeholders. ### 3) Changelog - **Added**: New features - **Improved**: Enhancements to existing features - **Fixed**: Bug fixes - **Deprecated**: Features being phased out - **Breaking**: Changes that require user action ### 4) Upgrade notes - **Steps**: What users need to do to upgrade - **Gotchas**: Common pitfalls to avoid ### 5) Test checklist (8 bullets) Key things to verify before release. ### 6) Announcement - **Short (280 chars)**: For Twitter/X - **Medium (2 paragraphs)**: For blog/newsletter - **Dev focused (bullets)**: Technical highlights
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.