li3p/changelog
skills/changelog/SKILL.md
Generate human-readable changelog entries from git history and diffs. Use when preparing release notes, summarizing commits since a tag, or translating implementation commits into user-facing changes.
testing
Updated Apr 23, 2026
$ install --global
skillsauthnpx skillsauth add li3p/skills changelogInstall 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 23, 2026, 11:09 PM32.9s1 file scanned
SKILL.md
- name:
- changelog
- description:
- Generate human-readable changelog entries from git history and diffs. Use when preparing release notes, summarizing commits since a tag, or translating implementation commits into user-facing changes.
Changelog
Generate a changelog entry for: $ARGUMENTS
If no range is provided, infer a sensible range from the most recent tag or the recent commit history.
Workflow
- Identify the commit range.
- Read commit messages and inspect diffs when a message is ambiguous.
- Ignore pure formatting, refactors, test-only changes, and internal churn unless they affect user-visible behavior or operational risk.
- Group entries into conventional sections:
- Added
- Changed
- Fixed
- Removed
- Security
- Infrastructure
- Write entries in user-facing language.
Output
Use this format:
## [version or range] - YYYY-MM-DD
### Added
- ...
### Changed
- ...
### Fixed
- ...
Include short commit hashes when helpful for traceability. Do not commit or edit files unless the user asks to update a changelog file.
Related Skills
li3p/notion-search
documentation
VerifiedTrustedCommunity
Search Notion for pages or databases by query using marknotion. Use when the user references a Notion page by name rather than URL, when locating a page to publish to or pull from, or when discovering what trackers and docs exist in the connected workspace.
SKILL.mdUpdated May 27, 2026
li3p/notion-pull
documentation
VerifiedTrustedCommunity
Export a Notion page to local Markdown using marknotion. Use when the user wants to pull a spec, design doc, meeting notes, or any Notion page into the repository as a Markdown file, or wants to read Notion content as context for a task.
SKILL.mdUpdated May 27, 2026
li3p/notion-publish
documentation
VerifiedTrustedCommunity
Publish a local Markdown file to a Notion page using marknotion. Use when the user wants to push README, docs, changelogs, or any Markdown content to Notion, either updating an existing page or creating a new one under a parent page.
SKILL.mdUpdated May 27, 2026
li3p/testmatch
testing
VerifiedTrustedCommunity
Generate tests that match an existing project's testing style. Use when adding coverage for a target file, function, bug fix, or edge case while preserving local conventions.
SKILL.mdUpdated Apr 23, 2026