update-changelog

Add an entry to CHANGELOG.md after implementing a feature, fix, or other notable change in this repo.

IndexedMIT

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/tomyou666-update-changelog

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Add an entry to CHANGELOG.md after implementing a feature, fix, or other notable change in this repo. Use when the user asks to update the changelog, or right after finishing a code change that should be logged.

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/update-changelog

What's inside

Skill name: update-changelog
Description: Add an entry to CHANGELOG.md after implementing a feature, fix, or other notable change in this repo. Use when the user asks to update the changelog, or right after finishing a code change that should be logged.
License: MIT
Instructions: 33 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Update Changelog

Edit `CHANGELOG.md` at repo root after implementing a change.

## Steps

1. Open `CHANGELOG.md`.
2. Add the entry under `## [Unreleased]` (create this section right after the intro lines if missing).
3. Under `[Unreleased]`, use one of these exact Japanese category subheadings:
   - `### 追加` - new feature
   - `### 修正` - fix / change to existing behavior
   - `### その他` - other (docs, chore, refactor)
4. If the category subheading already exists under `[Unreleased]`, append a bullet to it instead of duplicating the heading.
5. Write one bullet per change, in Japanese, matching the terse style of existing entries (e.g. `〜を追加`, `〜を修正`), no trailing period.
6. For a sub-detail, nest a bullet with 2-space indent under the parent bullet.
7. Do NOT bump the version number or add a new `## [x.y.z] - date` heading unless the user explicitly asks to release/bump version.
8. Never edit already-released version sections.

## Format reference

```
## [Unreleased]

### 追加

- 新機能の説明

### 修正

- 修正内容の説明
```

From tomyou666/skills, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Sep 27, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/tomyou666/skills
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from tomyou666

Cite this page

update-changelog skill. Agent Mart. https://agentmart.dev/skills/tomyou666-update-changelog (last updated 2026-10-24)