release-notes
Use only when writing release notes, changelogs, version summaries, migration notes, breaking change notices, upgrade guidance, and user-facing or developer-facing release announcements.
Works with
--- name: release-notes description: Use only when writing release notes, changelogs, version summaries, migration notes, breaking change notices, upgrade guidance, and user-facing or developer-facing release announcements. license: MIT --- # Release Notes ## Workflow 1. Identify audience: users, developers, admins, internal team, or customers. 2. Group changes into features, fixes, improvements, docs, deprecations, and breaking changes. 3. Put user impact before implementation detail. 4. Include upgrade steps and migration notes when behavior changes. 5. Mark known issues and rollback notes when relevant. ## Style - Use concise bullets. - Avoid internal ticket noise unless the audience needs it. - Call out breaking changes clearly. ## Verification - Check version, date, links, issue references, and compatibility notes. - Confirm every breaking change has guidance.
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.
