release-notes
Draft user-facing release notes for software, libraries, skillsets, and documentation releases. Use when Codex is asked to write release notes, summarize changes for a version, distinguish highlights from fixes, or prepare publication notes.
Works with
--- name: release-notes description: Draft user-facing release notes for software, libraries, skillsets, and documentation releases. Use when Codex is asked to write release notes, summarize changes for a version, distinguish highlights from fixes, or prepare publication notes. license: MIT --- # Release Notes ## Core Workflow 1. Identify version, date, audience, release type, source changes, and publication channel. 2. Group changes by user impact: highlights, new features, improvements, fixes, breaking changes, deprecations, docs, and validation. 3. Lead with what users can do now or what changed for them. 4. Call out migration, compatibility, security, or action-required notes clearly. 5. Keep internal implementation detail out unless it affects users or operators. 6. Verify commands, counts, links, and version names before finalizing. ## Safety Rules - Do not invent fixed issues, compatibility, performance gains, security status, or release dates. - Do not disclose private vulnerabilities or customer information. - Do not call a release stable if the source material says alpha, beta, draft, or preview. ## Deliverable Shape For release notes, provide: - Version and date - Highlights - New features - Improvements - Fixes - Breaking changes or migration notes - Validation - Known limitations or next roadmap ## References - Read `references/release-notes-checklist.md` when drafting or reviewing release notes.
More Writing & Documentation skills
paper-context-resolver
lllllllama/rigorpilot-skills
Rigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing README guidance by default.
repo-intake-and-plan
lllllllama/rigorpilot-skills
Rigor Intake helper for README-first deep learning repo reproduction. Use when the task is specifically to scan a repository, read the README and common project files, extract documented commands, classify inference, evaluation, and training candidates, and return the smallest trustworthy reproduction plan to the main orchestrator. Do not use for environment setup, asset download, command execution, final reporting, paper lookup, or end-to-end orchestration.
minimal-run-and-audit
lllllllama/rigorpilot-skills
Rigor Run skill for README-first deep learning repo reproduction. Use when the task is specifically to capture or normalize evidence from the selected smoke test or documented inference or evaluation command and write standardized `repro_outputs/` files, including patch notes when repository files changed. Do not use for training execution, initial repo intake, generic environment setup, paper lookup, target selection, hidden scientific-meaning changes, or end-to-end orchestration by itself.
