Skip to content
cccskills
FreePublished on GitHub

changelog-writer

Generate or update a CHANGELOG.md from merged commits and pull requests, grouped by change type and written for end users. Use when the user asks to write release notes, update the changelog, or summarize what changed between two versions or tags. Do not use for writing individual commit messages or for API-reference documentation.

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

Krusty84/SKILL.md-Inspector
See how to install

Files included (1)

  • SKILL.md2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Changelog Writer

Turn raw commit history into a changelog entry that a user of the project can read — not a mirror of the git log.

Workflow

  1. Find the range. Determine the span to describe: usually git log <last-tag>..HEAD. If no tag exists, ask the user for the starting point rather than guessing.
  2. Collect changes. Read the commit subjects and, where a commit is vague, the diff itself. Ignore merge commits, version bumps, and CI-only changes.
  3. Group and translate. Sort changes into these sections, omitting empty ones:
    • Added — new features
    • Changed — changes to existing behavior
    • Fixed — bug fixes
    • Deprecated / Removed — retired functionality
    • Security — vulnerability fixes Rewrite each item from the user's perspective: "Exports now include UTF-8 BOM so Excel opens them correctly", not "fix encoding in export.py".
  4. Write the entry. Follow the existing file's format if CHANGELOG.md already exists. Otherwise use Keep a Changelog style with a version heading and ISO date, e.g. ## [1.4.0] - 2026-07-19.
  5. Review. Re-read the entry and drop any item that a user of the project would not notice or care about.

Example

Input commits:

fix: handle nil pointer in csv export (#212)
chore: bump deps
feat: add --dry-run flag to sync command (#209)

Output entry:

## [1.4.0] - 2026-07-19

### Added
- `sync` now supports `--dry-run` to preview changes without writing (#209).

### Fixed
- CSV export no longer crashes on rows with empty optional fields (#212).

Rules

  • Never fabricate a change that is not in the history.
  • Keep PR/issue numbers when the project's existing changelog includes them.
  • New entries go at the top, above previous releases.

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

api-error-triage

Free

Diagnose failing HTTP API calls - 4xx/5xx responses, timeouts, TLS errors, and auth failures - by isolating the fault layer and producing a minimal reproduction. Use when the user reports an API request failing, pastes an HTTP error response or status code, or asks why a request works in one client but not another. Do not use for designing new APIs or for performance tuning of requests that already succeed.

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

Krusty84/SKILL.md-Inspector44Updated Aug 1, 2026

bug-repro-minimizer

Free

Reduce a failing test case, script, or input file to the smallest version that still reproduces a bug. Use when the user has a large reproduction and asks to minimize, bisect, or isolate it, or says things like "it stops failing when I remove half the file". Do not use when there is no reliable reproduction yet - help build one first, then minimize it.

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

Krusty84/SKILL.md-Inspector44Updated Aug 1, 2026

code-formatter

Free

Apply the team style guide to source files - naming conventions, comment style, and file organization. Use when the user asks to align code with the style guide or clean up naming.

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

Krusty84/SKILL.md-Inspector44Updated Aug 1, 2026

code-formatter

Free

Run the project's configured formatter (prettier, black, gofmt, rustfmt) on changed files and fix formatting-only CI failures. Use when the user asks to format code, fix a lint/format CI step, or normalize whitespace and import order. Do not use for logic changes or refactoring.

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

Krusty84/SKILL.md-Inspector44Updated Aug 1, 2026

csv-cleaner

Free

Clean and normalize messy CSV/TSV files - fix malformed rows, inconsistent headers, mixed encodings, stray delimiters, and duplicated records - and deliver a valid, verified file. Use when the user mentions a broken, messy, or malformed CSV, a file a spreadsheet tool refuses to open, or asks to deduplicate or normalize tabular data. Do not use when the deliverable is analysis or a chart rather than a cleaned file, or for Excel-native features like formulas and pivot tables.

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

Krusty84/SKILL.md-Inspector44Updated Aug 1, 2026

data-thing

Free

Does data things.

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

Krusty84/SKILL.md-Inspector44Updated Aug 1, 2026

See all skills by Krusty84

Report a problem with this skill