Agent skill
changelog
Use when updating CHANGELOG.md. Enforces consistent formatting with bolded item names, dash separators, and specific section ordering.
Install this agent skill to your Project
npx add-skill https://github.com/udecode/dotai/tree/main/.claude/skills/changelog
SKILL.md
Changelog Writing Style
Format
Based on Keep a Changelog.
Entry Structure
## [X.Y.Z] - YYYY-MM-DD
### Added/Changed/Fixed/Removed
- **`item-name`** - Description of change
- Sub-bullet for additional details
- Another detail if needed
Rules
- Bold item names - Always wrap in
**\item-name`**` (backticks inside bold) - Dash separator - Use
-between item name and description - Sentence case - Descriptions start with capital letter
- No periods - End descriptions without periods
- Sub-bullets - Indent with 2 spaces, use for details
Section Order
- Added
- Changed
- Fixed
- Removed
Only include sections with content.
Examples
Good:
- **`debug plugin`** - Renamed skill: systematic-debugging → debug
- **`/workflows:plan` command** - Interactive Q&A refinement phase (#88)
- After generating initial plan, now offers to refine with targeted questions
- Asks up to 5 questions about ambiguous requirements
Bad:
- debug plugin - renamed skill # missing bold/backticks
- **debug plugin**: renamed skill # colon instead of dash
- **`debug plugin`** - renamed skill. # has period
Versioning
- Major (X.0.0) - Breaking changes, major removals
- Minor (X.Y.0) - New features, new plugins
- Patch (X.Y.Z) - Bug fixes, renames, documentation
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
debug
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework with built-in backward tracing for deep-stack failures, ensuring root-cause understanding before implementation
tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
dig
Look up documentation and source code for libraries and packages. Use when the user asks a question about a library, needs to understand a library's API, or when you need information about a library that you don't know about. Triggers on questions like "How do I use X library?", "What's the API for Y?", "Show me how Z library handles this", or when encountering unfamiliar library usage.
verl-rl-training
Provides guidance for training LLMs with reinforcement learning using verl (Volcano Engine RL). Use when implementing RLHF, GRPO, PPO, or other RL algorithms for LLM post-training at scale with flexible infrastructure backends.
openrlhf-training
High-performance RLHF framework with Ray+vLLM acceleration. Use for PPO, GRPO, RLOO, DPO training of large models (7B-70B+). Built on Ray, vLLM, ZeRO-3. 2× faster than DeepSpeedChat with distributed architecture and GPU resource sharing.
gguf-quantization
GGUF format and llama.cpp quantization for efficient CPU/GPU inference. Use when deploying models on consumer hardware, Apple Silicon, or when needing flexible quantization from 2-8 bit without GPU requirements.
Didn't find tool you were looking for?