Skip to content
cccskills
FreePublished on GitHub

update-changelog

Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Update Changelog

Update the Unreleased section of the changelog based on the current changes.

Step 1: Run /changelog-rules Skill

Run the /changelog-rules skill to load shared changelog conventions.

Step 2: Check for Changelog

Use git rev-parse --show-toplevel to find the repository root. Look for the changelog file per /changelog-rules. If it does not exist, skip this skill. Do not create it.

Step 3: Analyze the Changes

Determine what changed:

  • Read git diff --cached for staged changes
  • If nothing is staged, read git diff for unstaged changes
  • Use the conversation context for the intent behind the changes

Step 4: Assess Changelog-Worthiness

Apply the /changelog-rules changelog-worthiness and net-delta criteria. Skip fixes to code introduced by the same branch or PR.

If no changes are changelog-worthy, skip this skill.

Step 5: Check Existing Unreleased Entries

Read the current Unreleased section of the changelog. Look for entries that relate to the same feature or fix. This prevents duplicates across multiple commits for the same body of work.

  • If an existing entry covers the same change, update its wording only if the current commit meaningfully extends or refines the feature. Do not add a duplicate entry.

Step 6: Update the Unreleased Section

Add or update entries in the Unreleased section following /changelog-rules conventions. Create subsection headers as needed (e.g., ### Added).

Then use the TaskList tool and proceed to any remaining task.

Rules

  • Never modify released version sections. Only the Unreleased section is in scope.
  • Do not stage the modified file. Staging is handled separately.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to "apply findings", "apply fixes", "apply suggestions", "apply accepted findings", "fix the findings", or "apply the review results".

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 22, 2026

Audit the turbo skill lessons that /self-improve writes into this repo's .turbo/handoff/ from other projects, apply the ones the user approves, delete the consumed handoffs, commit and push, and update the installed Turbo skills. Use when the user asks to "read .turbo/handoff and let me know what you think", "read the handoff files and let me know what you think", "review the lesson handoffs", "apply the self-improve handoffs", or "process the turbo handoffs".

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 22, 2026

Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", "what's our worst code", "find low-value tests", or "which tests can we delete". Analysis-only — does not modify code.

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 22, 2026

Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 22, 2026

Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 22, 2026

Run a non-interactive Claude Code print-mode call from Codex. Use when the user asks to "claude print", "ask claude", "run claude", "consult claude", or when a Codex Turbo skill needs Claude as an independent peer reviewer.

The English summary is being prepared. Showing the original description.

tobihagemann/turbo415Updated Oct 22, 2026

See all skills by tobihagemann

Report a problem with this skill