Agent skill

changelog

Use when updating CHANGELOG.md. Enforces consistent formatting with bolded item names, dash separators, and specific section ordering.

Stars 1,141
Forks 82

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

markdown
## [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

  1. Bold item names - Always wrap in **\item-name`**` (backticks inside bold)
  2. Dash separator - Use - between item name and description
  3. Sentence case - Descriptions start with capital letter
  4. No periods - End descriptions without periods
  5. Sub-bullets - Indent with 2 spaces, use for details

Section Order

  1. Added
  2. Changed
  3. Fixed
  4. Removed

Only include sections with content.

Examples

Good:

markdown
- **`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:

markdown
- 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

Expand your agent's capabilities with these related and highly-rated skills.

udecode/dotai

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

1,141 82
Explore
udecode/dotai

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.

1,141 82
Explore
udecode/dotai

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.

1,141 82
Explore
davila7/claude-code-templates

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.

23,776 2,298
Explore
davila7/claude-code-templates

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.

23,776 2,298
Explore
davila7/claude-code-templates

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.

23,776 2,298
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results