changelog-release-notes
starsforks
How to install changelog-release-notes?
nowledge-co/con-terminal/changelog-release-notes
$npx -y skills add nowledge-co/con-terminal --skill changelog-release-notesMaintain Con's CHANGELOG.md and release notes. Use when updating changelog entries, preparing a beta/dev release, reviewing PR release-note coverage, or ensuring contributor PR credit is present.
SKILL.md
| 1 | # Changelog Release Notes |
| 2 | |
| 3 | Use this skill whenever `CHANGELOG.md`, PR release notes, or release summaries |
| 4 | are touched. |
| 5 | |
| 6 | ## Workflow |
| 7 | |
| 8 | 1. Verify the latest released beta before choosing a heading: |
| 9 | - `git fetch --tags origin` |
| 10 | - `git tag --sort=-v:refname | rg '^v[0-9]+\\.[0-9]+\\.[0-9]+-beta\\.' | head` |
| 11 | - `gh release view <tag>` when GitHub release state matters |
| 12 | 2. Put pending work under the next unreleased beta only. If the latest shipped |
| 13 | beta is `v0.1.0-beta.63`, the top unreleased heading is |
| 14 | `v0.1.0-beta.64`; do not create `beta.65` until `beta.64` is tagged and |
| 15 | released. |
| 16 | 3. Gather PR and author context for every entry: |
| 17 | - `gh pr view <number> --json number,title,author,url,mergedAt` |
| 18 | - for merged work, `git log <latest-tag>..HEAD --merges --oneline` helps |
| 19 | find the included PRs |
| 20 | 4. Every PR-derived changelog bullet must end with PR and author credit: |
| 21 | - `_(PR [#149](https://github.com/nowledge-co/con-terminal/pull/149) by [@sundy-li](https://github.com/sundy-li))_` |
| 22 | 5. Credit contributors exactly by GitHub login. Preserve external contributor |
| 23 | credit even when follow-up commits refine the same feature. |
| 24 | 6. Keep shipped historical sections stable. Only edit old sections to correct a |
| 25 | factual mistake, missing credit, or broken link. |
| 26 | |
| 27 | ## Writing Rules |
| 28 | |
| 29 | - Write for users first: describe the visible behavior or benefit, not the |
| 30 | internal implementation unless it explains a risk or platform boundary. |
| 31 | - Use `Added`, `Changed`, and `Fixed` sections. Group bullets under concise |
| 32 | audience/platform labels such as `macOS`, `Windows, Linux`, `Panes`, or |
| 33 | `Developer Experience`. |
| 34 | - Do not mention "workspace restore" or other baseline continuity as novelty |
| 35 | unless the user-facing behavior truly changed. Default expected behavior |
| 36 | should read as polish or reliability, not marketing. |
| 37 | - Add release dates only when a version is actually tagged/released. |
| 38 | - If a bullet combines multiple PRs, include all relevant PR/author credits. |
| 39 | |
| 40 | ## Validation |
| 41 | |
| 42 | - Confirm the heading matches the latest shipped beta plus one. |
| 43 | - Confirm every new PR-derived bullet has `PR [#...]` and `by [@...]`. |
| 44 | - Run `python3 scripts/docs/validate-manifest.py` when docs routing may be |
| 45 | affected. |
| 46 | - Run `git diff --check` before committing. |
People who liked this also viewed
6 picksType
- find-skillsHelps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skSkillsJul 2026
- grill-meA relentless interview to sharpen a plan or design.SkillsJul 2026
- vercel-react-best-practicesVercel's official collection of agent skillsSkillsJul 2026
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.SkillsJul 2026
- setup-matt-pocock-skillsConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.SkillsJul 2026
- triageMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.SkillsJul 2026
