Use when updating a CHANGELOG or preparing release notes. Turns merged changes into Keep a Changelog entries written for users.
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add babarmuhammad/claudectl --skill changelog --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Changelog?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/babarmuhammad-changelog)More formats (shields.io, HTML) on the badges page.
---
name: changelog
description: Use when updating a CHANGELOG or preparing release notes. Turns merged changes into Keep a Changelog entries written for users.
---
# Changelog writer
Maintain a human-readable changelog that tells users what changed.
## Steps
1. Read the existing `CHANGELOG.md` (follow its style) or start one in **Keep a Changelog** format.
2. Gather changes since the last release (`git log <last-tag>..HEAD`, merged PRs).
3. Group under an `## [Unreleased]` (or new version) heading using these sections, omitting empty ones:
`Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security`.
4. Write each entry from the **user's** point of view — the effect, not the commit text — one line each.
5. On release, rename `Unreleased` to `## [x.y.z] - YYYY-MM-DD` and bump per semver.
## Rules
- User-facing impact only; skip internal refactors and test-only changes unless they affect users.
- Link issues/PRs where it helps.
- Newest version on top; keep entries terse and parallel in phrasing.
<!-- claudectl starter skill. Follows Keep a Changelog (keepachangelog.com) +
Semantic Versioning; inspired by release skills in the ecosystem. -->
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
