changelog

Included with Lifetime

$97 forever

Auto-generates CHANGELOG.md entries from git history using Keep a Changelog format. Analyzes commits since last recorded entry, filters noise, reviews diffs, and groups changes into Added/Changed/Fixed/Removed sections.

General

What this skill does


# Changelog Skill

Generate CHANGELOG.md entries from git history using [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) format.

## Capabilities

- Read existing CHANGELOG.md and detect where to insert new entries
- Analyze git history since last recorded commit
- Filter out noise commits (changelog-only, config-only changes)
- Review actual diffs to write accurate, user-facing descriptions
- Group changes into standard sections: Added, Changed, Fixed, Removed

## Usage

This skill activates when:
- User asks to "update the changelog"
- User asks to "generate changelog entries"
- User wants to "add recent changes to CHANGELOG.md"
- User mentions "changelog" in context of git history

## Approach

### Step 1: Read Current State

Read `CHANGELOG.md` in the project root. Extract the last recorded commit hash from the first `## ... \`hash\`` header line.

- If CHANGELOG.md does not exist, create one with a title and description header
- If no hash is found in any header, fall back to the repository's initial commit

### Step 2: Get New Commits

Run:
```bash
git log <LAST_HASH>..HEAD --format="%h %s" --reverse
```

If there are no new commits, inform the user and stop.

### Step 3: Filter Noise Commits

Skip commits that ONLY touch:
- `CHANGELOG.md`
- `CLAUDE.md` or `.claude/` files
- `.gitignore`
- Dev config files (editor settings, linter configs) with no functional code changes

### Step 4: Review Diffs

For each remaining commit, review the actual diff:
```bash
git diff <HASH>^..<HASH>
```

Diffs are the source of truth — do not rely solely on commit messages.

### Step 5: Group and Write Entries

Group changes into sections (omit empty ones):
- **Added** — New features or capabilities
- **Changed** — Modifications to existing functionality
- **Fixed** — Bug fixes
- **Removed** — Removed features or capabilities

Merge related commits into single bullets. Write concise, user-facing descriptions. Reference the git hash each entry covers through.

### Step 6: Format Header

Use the author date of HEAD:
```bash
git log -1 HEAD --format="%h %ai"
```

Header format:
```
## YYYY-MM-DD HH:mm:ss `SHORT_HASH`
```

### Step 7: Insert Entry

Insert the new entry after the CHANGELOG.md header block (title + description paragraph), before the first existing `##` entry.

### Step 8: Report

Tell the user what was added. Do NOT commit the changes — leave that to the user.

## Output Format

The generated CHANGELOG.md entry follows this structure:

```markdown
## 2026-03-16 14:30:00 `abc1234`

### Added
- New feature description (`def5678`)

### Changed
- Modified behavior description (`abc1234`)

### Fixed
- Bug fix description (`789abcd`)
```

## Notes

- Each entry references the git hash it covers through
- Description paragraph in CHANGELOG.md: "Maintained with the help of AI tooling. Each entry references the git hash it covers through."
- Keep bullets concise and user-facing — avoid implementation details
- When multiple commits relate to the same feature, merge them into one bullet

Files: 1

Size: 3.2 KB

Complexity: 7/100

Category: General

Source: https://github.com/tasanakorn/cc-marketplace/tree/main/plugins/changelog/skills/changelog

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts