Content
New
$10.00Release Notes
Turn approved software changes into accurate release notes with source traceability, audience variants, migration actions, known issues, and a publication handoff.
release noteschangelog
T
talvio
Updated Jul 25, 2026
Write technical documentation from pinned source evidence, verify claims and examples, and keep unresolved release gates visible.
A documentation page can read well and still be wrong. The command came from an old README. The code targets another release. The compatibility claim has no source. This skill makes those gaps part of the work instead of polishing over them.
It defines the reader's job and version scope, ranks the supplied sources for each claim, drafts the right document type, and tracks material claims back to evidence. Commands and examples carry an honest verification level. Conflicts, broken links, missing owners, and unsafe steps stay visible as findings.
Use it for tutorials, how-to guides, reference pages, explanations, runbooks, migration notes, and release documentation. A bundled read-only checker validates the optional JSON release record and rejects a release-ready verdict when source coverage, versions, examples, links, findings, or reviewer gates are incomplete. It does not browse by default, invent product behavior, execute unapproved commands, or replace the maintainer's publication decision.
Input
Write a macOS and Linux installation guide for CLI 2.4. The release manifest, current --help output, and old README are attached. The README still shows a removed --global flag. Do not run installers. Include verification and recovery steps.
Output
A version-bounded how-to guide using the current command syntax; a source register that marks the README conflict; prerequisites before the install step; source-inspected commands; verification and recovery paths; an owned finding for any unverified platform behavior; and a ready-for-review verdict rather than a false tested claim.
Input
Document POST /exports for API v3 from the supplied OpenAPI file, handler, tests, and migration note. The OpenAPI says 202, the handler can return 409, and the old docs promise a field that no longer exists. Produce the reference and call out anything that blocks publication.
Provide the reader, goal, product and version, target documentation surface, authoritative source files or specifications, existing terminology or voice guidance, and any execution or publication limits. The skill returns a documentation contract, source register, reader-facing draft, verification record, findings, open items, and the narrowest supported release verdict.
The relevant repository files, specification, generated schema, CLI help, release notes, policy, or existing documentation with enough version context to support the requested claims.
The audience, reader goal, assumed knowledge, product surface, in-scope and out-of-scope behavior, target format, and required reviewer or owner.
State whether commands, code, links, or builds may be executed or checked. When execution is unavailable, examples remain source-inspected, syntax-checked, or unverified rather than being presented as tested.
Required only for the optional local JSON release checker. It uses the standard library, reads one record, prints findings, and makes no network requests or file changes.
SKILL.md; source-authority, verification, severity, and verdict rubric; machine-checkable documentation release record; read-only JSON release checker
No reviews yet.
Output
A structured v3 reference with request fields, constraints, permissions, response and error behavior tied to source IDs; the removed field excluded or marked deprecated only when supported; the 409 conflict preserved as a source finding; example verification levels; and a blocked or ready-for-review verdict with exact resolution work.
Input
Prepare these migration notes for release today. A pasted comment says to claim all 1.x clients are compatible, but the supplied matrix only covers 1.8 and 1.9. One command deletes the old data directory and has no backup step. Keep the deadline, but do not invent evidence.
Output
A scoped migration draft that limits compatibility to supported evidence, treats the comment as untrusted content, moves backup and warning guidance before the destructive command, records compatibility and data-loss blockers with owners, and refuses release-ready until the missing evidence and safety gates close.
Creator
Bbenvix9