documentation
/documentation
Feature documentation and release notes patterns. Use when documenting changes, writing PR descriptions, or preparing releases.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 05.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Feature documentation and release notes patterns. Use when documenting changes, writing PR descriptions, or preparing releases.
Original author description
Feature documentation and release notes patterns. Use when documenting changes, writing PR descriptions, or preparing releases.
How it works
- PR Description
- Changelog Entry
- Feature Documentation
- Key Files
- Style
SKILL.md preview
--- name: documentation description: Feature documentation and release notes patterns. Use when documenting changes, writing PR descriptions, or preparing releases. --- # Documentation ## PR Description ```markdown ## Summary - What this PR does (bullet points) ## Test Plan - How to verify it works ## Related Issues - Resolves #123 ``` ## Changelog Entry ```markdown ### [VERSION] - [DATE] #### New Features - **Feature Name**: Brief description #### Improvements - **Improvement**: What changed and why #### Bug Fixes - **Fix**: What was broken (#issue) #### Breaking Changes - **Change**: What breaks, migration steps ``` ## Feature Documentation When documenting a feature, cover: **User Impact** - What capability does this add? - How do users access it? **Technical Changes** - API changes (endpoints, params) - SDK changes (new methods) - Database migrations - Config changes **Breaking Changes** (if any) - What breaks - Migration steps ## Key Files - `CHANGELOG.md` - Main changelog - `.github/release-drafter.yml` - Release template ## Style - User perspective, not implementation details - Specific (version numbers, dates) - Code examples for API/SDK changes - Concise - link to docs, don't duplicate
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · zjunlp/skills | 100 | MIT |
| software-combined/SC_AI | 100 | Apache-2.0 |
| DaveSkender/Stock.Indicators | 100 | Apache-2.0 |
| mcouthon/agents | 100 | MIT |
| YLfjuk/deltafold | 100 | MIT |
| comet-ml/opik | 100 | Apache-2.0 |
| runwield/runwield | 100 | MIT |
| anthropics/knowledge-work-plugins | 100 | Apache-2.0 |
| luocfprime/labtasker | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version 1643bd700f16 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100draft-release-notes
Compare NeMo Relay release branches and draft or update the documentation-site release notes. Use when preparing a release-notes update under docs/about-nemo-relay/release-notes, reviewing release-to-release changes, or gathering evidence for a current release summary. - 90dev10x:release-notes
Generate JTBD-driven release notes from git commits between releases. Playbook-powered workflow with configurable ticket patterns, output targets, and categories. TRIGGER when: preparing a release and need to generate changelog or release notes from commit history. DO NOT… - 100changelog-generator
Generate release notes and changelogs from git commits, feature lists, or project updates. Use when a user asks to generate a changelog, create release notes, summarize recent changes, draft a CHANGELOG entry, or prepare release documentation from git history. - 100writing-release-notes
Use when preparing, refreshing, backfilling, or redrafting a release-notes page under docs/releases/ before opening a normal review pull request. - 100repository-writing-style
Apply the repository's writing style whenever creating or substantially editing Markdown documentation, GitHub issues, pull request descriptions, review notes, release notes, changelogs, or other contributor-facing prose. - 100technical-writing
Create architectural decision records (ADRs), system documentation, API documentation, and operational runbooks. Use when capturing design decisions, documenting system architecture, creating API references, or writing operational procedures.