kjanat/changelog-writing
skills/changelog-writing/SKILL.md
Write and maintain changelogs following the Keep a Changelog convention. Use when creating a CHANGELOG.md, adding entries for a release, or reviewing changelog format and completeness.
development
Updated Apr 18, 2026
$ install --global
skillsauthnpx skillsauth add kjanat/skills changelog-writingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 7:22 AM34.1s2 files scanned
SKILL.md
- name:
- changelog-writing
- description:
- Write and maintain changelogs following the Keep a Changelog convention. Use when creating a CHANGELOG.md, adding entries for a release, or reviewing changelog format and completeness.
- license:
- MIT
- author:
- kjanat
- version:
- 1.0
Changelog Writing
Write changelogs for humans, not machines. Follow the Keep a Changelog convention.
Format Rules
- File:
CHANGELOG.mdat project root - Date format: ISO 8601 (
YYYY-MM-DD) - Latest version first (reverse chronological)
- One entry per version, every version documented
- Follow Semantic Versioning
- Version headings are linkable (comparison URLs at bottom)
Change Categories
Group changes under these headings, in this order:
| Category | Use for |
| ------------ | ---------------------------------- |
| Added | New features |
| Changed | Changes to existing functionality |
| Deprecated | Features marked for future removal |
| Removed | Features removed in this release |
| Fixed | Bug fixes |
| Security | Vulnerability patches |
Omit empty categories. Never invent new category names.
Unreleased Section
Always keep an ## [Unreleased] section at the top:
## [Unreleased]
### Added
- New user profile endpoint.
At release time, move Unreleased entries into a new versioned heading.
Version Heading Format
## [1.2.0] - 2025-08-15
Yanked releases append [YANKED]:
## [1.1.0] - 2025-07-01 [YANKED]
Comparison Links
At the bottom of the file, define diff links for every version:
[Unreleased]: https://github.com/org/repo/compare/v1.2.0...HEAD
[1.2.0]: https://github.com/org/repo/compare/v1.1.0...v1.2.0
[1.1.0]: https://github.com/org/repo/releases/tag/v1.1.0
Anti-Patterns
| Don't | Why |
| -------------------------- | ------------------------------------------- |
| Dump git log as changelog | Noise: merge commits, docs changes, typos |
| Skip deprecation notices | Users can't prepare for breaking changes |
| Use regional date formats | Ambiguous (01/02/03). Use ISO 8601 |
| Document only some changes | Partial changelog is worse than none |
| Use GitHub Releases alone | Non-portable, less discoverable than a file |
Writing Style
- Write entries as imperative statements from the user's perspective
- Focus on what changed for the user, not implementation details
- Be specific: "Add dark mode toggle in settings" not "Update UI"
- Group related changes into a single entry when appropriate
Reading Order
| Task | Files to Read | | -------------------- | ----------------------- | | Create new CHANGELOG | SKILL.md + example.md | | Add release entries | SKILL.md (categories) | | Review format | SKILL.md (format rules) | | See full example | example.md |
In This Reference
| File | Purpose | | ----------------------------------- | -------------------------- | | example.md | Complete example changelog |
Related Skills
kjanat/statute-proxy
development
VerifiedTrustedCommunity
Use this skill whenever the user is designing, building, scaffolding, reviewing, or debugging Go-based reverse proxy or HTTP edge infrastructure, especially when they mention statute, config-as-code proxies, building an nginx replacement in Go, networking topology, TLS termination, load balancing, HTTP/2, HTTP/3, QUIC, ACME, upstream pools, middleware chains, or graceful shutdown. Trigger this skill even when the user does not explicitly name statute but is clearly working on a Go HTTP server, edge proxy, or networking infrastructure problem where the resulting artefact will be a compiled binary rather than a runtime-configured server. Also trigger when the user asks for explanations of networking protocols (HTTP/1.1, HTTP/2, HTTP/3, WebSockets, gRPC, TLS) in the context of building or operating a proxy, or when they ask about Go net/http pitfalls, transport tuning, or production-grade server defaults.
SKILL.mdUpdated May 8, 2026
kjanat/threlte
development
VerifiedTrustedCommunity
Routes Threlte questions to exact, commit-pinned docs paths and practical workflows. Use when helping with setup, debugging, or architecture across @threlte/core, @threlte/extras, @threlte/gltf, @threlte/rapier, @threlte/theatre, @threlte/xr, @threlte/flex, and @threlte/studio.
SKILL.mdUpdated Apr 18, 2026
kjanat/lightning
testing
VerifiedTrustedCommunity
Comprehensive lightning physics knowledge base derived from Rakov & Uman (2003) "Lightning: Physics and Effects". Covers discharge types, current parameters, leader/return-stroke physics, cloud electrification, protection, detection systems, atmospheric effects, and quantitative reference data. Use when answering questions about lightning physics, electromagnetic fields, thunderstorm electricity, lightning protection, or atmospheric electrical phenomena.
SKILL.mdUpdated Apr 18, 2026
kjanat/index-knowledge
development
VerifiedTrustedCommunity
Generate hierarchical AGENTS.md knowledge base for a codebase. Creates root + complexity-scored subdirectory documentation.
SKILL.mdUpdated Apr 18, 2026