Update Changelog Agent Skill
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\".
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/tobihagemann/turbo --skill update-changelogThe instruction itself
8 sections, as written by the authorUpdate Changelog
Update the Unreleased section of the changelog based on the current changes.
Step 1: Run /changelog-rules Skill
Run /changelog-rules 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 --cachedfor staged changes - If nothing is staged, read
git difffor 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.
Other skills for the same job
different authors, same section of the catalogue
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
How to use it
Take tobihagemann/update-changelog from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.