changelog

changelog is a cursor rule for Cursor from Pranav-Karra-3301/tuck. It costs 0 tokens per session (511 once invoked), scanned A, original, MIT.

Project rules for generating a CHANGELOG.md file and release notes from commit messages. A changelog is a record of changes made between software versions.

In plain words
What is it for?
Use it when writing commits or preparing releases so semantic-release can update the changelog, package version, npm publication, and GitHub release.
Why use it?
It makes release notes follow a consistent format and connects commit types such as features and fixes to version changes.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when writing commits or preparing releases so semantic-release can update the changelog, package version, npm publication, and GitHub release.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/pranav-karra-3301/tuck/changelog
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/Pranav-Karra-3301/tuck

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for changelog

README.md
[![agentmods](https://agentmods.dev/badge/rules/pranav-karra-3301/tuck/changelog/github.svg)](https://agentmods.dev/rules/pranav-karra-3301/tuck/changelog)
Your own site
<a href="https://agentmods.dev/rules/pranav-karra-3301/tuck/changelog"><img src="https://agentmods.dev/badge/rules/pranav-karra-3301/tuck/changelog/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for changelog

Your own site · 80×15
<a href="https://agentmods.dev/rules/pranav-karra-3301/tuck/changelog"><img src="https://agentmods.dev/badge/rules/pranav-karra-3301/tuck/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 511 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00511
Opus 5 $0.00000 $0.00255
Sonnet 5 $0.00000 $0.00102
Haiku 4.5 $0.00000 $0.00051

Measured 9d ago against content hash 1cb695a71d68, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

changelog scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/changelog.mdc · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Changelog Rules

Automatic Generation

CHANGELOG.md is automatically generated by semantic-release based on commit messages.

How It Works

  1. Commits to main trigger release workflow
  2. semantic-release analyzes commit messages
  3. Version is determined by commit types
  4. CHANGELOG.md is updated automatically
  5. npm package is published
  6. GitHub release is created

Commit Message Impact

Commit Type Version Bump Changelog Section
feat: Minor (0.x.0) Features
fix: Patch (0.0.x) Bug Fixes
perf: Patch (0.0.x) Performance
BREAKING CHANGE Major (x.0.0) Breaking Changes
docs: None Not included
style: None Not included
refactor: None Not included
test: None Not included
chore: None Not included

Writing Good Commit Messages

For meaningful changelog entries:

# Good - describes user-facing change
feat: add restore command for backup recovery
fix: prevent data loss when sync fails mid-operation

# Bad - too vague
feat: add new feature
fix: fix bug

Breaking Changes

Mark breaking changes clearly:

feat!: redesign configuration file format

BREAKING CHANGE: The config.json format has changed.
Users must migrate their configuration files using
the new 'tuck config migrate' command.

Manual Changelog Edits

NEVER manually edit CHANGELOG.md:

  • It will be overwritten by semantic-release
  • Use commit messages to control content
  • Use conventional commits format

Release Notes

GitHub releases are created automatically with:

  • Version number from package.json
  • Changelog entries for this version
  • Links to commits and PRs
  • Binary artifacts attached

Changelog Format

The generated changelog follows Keep a Changelog format:

# Changelog

## [1.2.0] - 2024-01-15

### Features

* add restore command for backup recovery (abc1234)

### Bug Fixes

* prevent data loss when sync fails (def5678)

Read the full file on GitHub · 93 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 93 lines · 0 tokens per session scan A 1cb695a71d68

Subscribe to this mod's changes

changelog is a cursor rule published in the GitHub repository Pranav-Karra-3301/tuck (15 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 511 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.