Skill
agent-communication
AI DevKit · Exchange information with active Codex, Claude Code, and other AI agents using ai-devkit agent list, detail, and send. Use when an agent needs to…
@codeaholicguyView SkillDevelopment
Skill
/changelog
AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.
Install
$ npx -y skills add codeaholicguy/ai-devkit --skill changelog --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/changelog
Context preview
The summary Claude sees to decide when to auto-load this skill.
AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.
SKILL.md
changelog.SKILL.mdname: changelog
description: AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.
Changelog
Update the top `Unreleased` list in `CHANGELOG.md` from commits after the latest release.
Workflow
1. Find the latest release base:
- Prefer the latest reachable tag: `git describe --tags --abbrev=0`.
- If there are no tags, search recent history for a release commit and use that hash.
2. Get commits: `git log <base>..HEAD --reverse --format='%H%x09%s'`. 3. Derive the GitHub repo URL from `git remote get-url origin`. 4. For each commit, add one concise changelog line:
- Format: `- [<short-hash>](<url>) <one-line summary>`
- If the commit clearly relates to a PR, link the hash to the PR URL instead of the commit URL.
- Detect PRs from subjects like `(#123)`, merge commits, or `gh pr list --search <hash> --state all --json number,url`.
5. Insert the new lines into the top `Unreleased` section/list in `CHANGELOG.md`.
- If no `Unreleased` section exists, create one at the top.
- Do not create a dated release heading unless the user asks for a release.
Rules
- Keep one line per commit.
- Preserve the existing changelog style when obvious.
- Always add entries to the top `Unreleased` list.
- Skip noisy commits only when clearly non-user-facing and explain what was skipped.
- Do not invent PR links; use commit links when PR evidence is missing.
Read more
name: changelog description: AI DevKit · Update CHANGELOG.md Unreleased items from git commits since the latest release. Use when users ask to update changelog/release notes from recent commits, with one concise line per commit and commit/PR links.
Changelog
Update the top `Unreleased` list in `CHANGELOG.md` from commits after the latest release.
Workflow
1. Find the latest release base:
- Prefer the latest reachable tag: `git describe --tags --abbrev=0`.
- If there are no tags, search recent history for a release commit and use that hash.
2. Get commits: `git log <base>..HEAD --reverse --format='%H%x09%s'`. 3. Derive the GitHub repo URL from `git remote get-url origin`. 4. For each commit, add one concise changelog line:
- Format: `- [<short-hash>](<url>) <one-line summary>`
- If the commit clearly relates to a PR, link the hash to the PR URL instead of the commit URL.
- Detect PRs from subjects like `(#123)`, merge commits, or `gh pr list --search <hash> --state all --json number,url`.
5. Insert the new lines into the top `Unreleased` section/list in `CHANGELOG.md`.
- If no `Unreleased` section exists, create one at the top.
- Do not create a dated release heading unless the user asks for a release.
Rules
- Keep one line per commit.
- Preserve the existing changelog style when obvious.
- Always add entries to the top `Unreleased` list.
- Skip noisy commits only when clearly non-user-facing and explain what was skipped.
- Do not invent PR links; use commit links when PR evidence is missing.
Ships withai-devkit
The control plane for AI coding agents. AI DevKit gives Claude Code, Codex CLI, Gemini CLI, opencode, Pi, Cursor, GitHub Copilot, Devin, and other coding agents one local-first operating layer: one config, one console, local memory retrieval, cross-agent
Get the whole plugin
Stats
1,624
Stars
250
Forks
Active
Maintenance
TypeScript
Language
Apache-2.0
License
1d ago
Last commit
11mo ago
Created
Repo: codeaholicguy/ai-devkit
Other skills on ai-devkit.
@codeaholicguyView SkillSkill
agent-management
AI DevKit · Manage running AI agents with ai-devkit agent commands. Use when an agent needs to identify itself, list agents, start workers, inspect agent…
@codeaholicguyView SkillSkill
agent-orchestration
AI DevKit · Supervise multi-agent workflows over repeated passes: poll progress, unblock waiting agents, coordinate dependencies, relay outputs, resolve…
@codeaholicguyView SkillSkill
ai-devkit-setup
AI DevKit · Check local AI DevKit readiness and run setup only when status shows onboarding or harness integration gaps.
@codeaholicguyView SkillSkill
brainstorm
AI DevKit · Use when the user asks to brainstorm, ideate, generate ideas, expand options, challenge ideas, pressure-test ideas, compare concepts, narrow…
@codeaholicguyView SkillSkill
dev-commit
AI DevKit · Safe git commit workflow for AI coding agents. Use when the user asks to commit, prepare a commit, stage changes, create a PR-ready checkpoint, or…
@codeaholicguyView Skill