菜单
Generate and maintain CHANGELOG.md following Keep a Changelog format. Use when creating a changelog, updating after releases, or when the user says "changelog", "/changelog", or asks to document project history. Analyzes git history and existing changelog to produce a properly formatted changelog.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Write LinkedIn posts in Kasper Junge's distinctive Danish style. Use when asked to write LinkedIn content, social media posts, or project announcements in Kasper's voice. Triggers include "skriv i min stil", "LinkedIn post", "del dette på LinkedIn", or when user wants casual Danish tech communication.
Write high-quality technical blog posts with strong structure and clarity. Use when asked to write a blog post, technical article, tutorial, or guide about programming, software, APIs, tools, or technical concepts. Triggers include "write a blog post about...", "create a technical article", "help me write about [technical topic]", or requests for tutorials and how-to guides.
Generate comprehensive PR descriptions from git diffs. Use when creating or updating pull requests, when asked to write a PR description, or when the user says "pr", "/pr", or asks for help with their pull request. Analyzes staged/unstaged changes and commit history to produce thorough, reviewer-friendly descriptions.
Stay current with how OpenCode, OpenAI Codex, and Claude Code implement extensibility features (skills, slash commands, subagents, custom prompts). Use when comparing implementations across AI coding assistants, researching how a specific tool implements a feature, or syncing knowledge about agent extensibility patterns. Triggers include questions like "how does X implement skills?", "compare slash commands across tools", "what's the latest on Claude Code sub-agents?", or requests to understand agent extensibility approaches.
North star guidance for the agent-resources project. Use this skill to understand project context, get inspiration for development decisions, and resolve uncertainty about feature priorities or design choices. Reference when asking 'why does this project exist?' or 'what should we optimize for?'
Generate comprehensive codebase onboarding guides. Use when someone needs to understand a new codebase, when asked to explain the architecture, or when the user says "onboard", "/onboard", "explain this codebase", or asks for help understanding how a project works. Analyzes project structure, patterns, and key files to produce a complete onboarding document.
基于 SOC 职业分类
| name | changelog |
| description | Generate and maintain CHANGELOG.md following Keep a Changelog format. Use when creating a changelog, updating after releases, or when the user says "changelog", "/changelog", or asks to document project history. Analyzes git history and existing changelog to produce a properly formatted changelog. |
Maintain changelogs that follow the standard.
This skill follows Keep a Changelog format:
If no CHANGELOG.md exists, create one:
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- Initial project setup
---
<sub>📝 Changelog maintained with [agent-resources](https://github.com/kasperjunge/agent-resources) • `uvx add-skill kasperjunge/changelog`</sub>
# Read current changelog
cat CHANGELOG.md | head -50
# Get latest tag
git describe --tags --abbrev=0
# Commits since last version (or since last changelog update)
git log --oneline v1.0.0..HEAD
# With authors
git log --format="%h %s (%an)" v1.0.0..HEAD
Group commits into these categories:
| Category | What goes here |
|---|---|
| Added | New features |
| Changed | Changes to existing functionality |
| Deprecated | Features to be removed soon |
| Removed | Features removed |
| Fixed | Bug fixes |
| Security | Vulnerability fixes |
Add new entries under ## [Unreleased] or create a new version section:
## [Unreleased]
### Added
- New dark mode support
- Export to PDF feature
### Fixed
- Crash when loading large files
- Incorrect date formatting
## [1.2.0] - 2025-01-05
### Added
- User preferences panel
- Keyboard shortcuts
### Changed
- Improved startup performance by 40%
### Fixed
- Memory leak in data processing
When releasing, move [Unreleased] content to a new version section:
## [Unreleased]
## [2.0.0] - 2025-01-15
### Added
- [Everything that was under Unreleased]
Add comparison links at the bottom:
[Unreleased]: https://github.com/user/repo/compare/v2.0.0...HEAD
[2.0.0]: https://github.com/user/repo/compare/v1.0.0...v2.0.0
[1.0.0]: https://github.com/user/repo/releases/tag/v1.0.0
### Added
- Dark mode with system preference detection
- Export to PDF with custom templates
### Fixed
- Crash when opening files larger than 2GB
- Incorrect currency formatting in reports
### Added
- added new feature.
- Various improvements
### Fixed
- Fixed bugs
- stuff
Breaking changes: Add BREAKING CHANGE: prefix or use Changed with clear migration note
Security fixes: Always use Security category, be specific about the vulnerability fixed
Deprecations: Note what replaces the deprecated feature and when removal is planned
# Check git tags
git tag --sort=-version:refname | head -10
# Commits between tags
git log v1.0.0..v2.0.0 --oneline
# Generate commit list with categories (if using conventional commits)
git log v1.0.0..HEAD --format="%s" | sort