What is release-changelog?

Release rules for the dbt-doctor project, including changelog updates, version numbering, tests, package tags, and publishing steps.

Use them when preparing a version bump or publishing dbt-doctor packages. They explain how to use Keep a Changelog, Changesets, and semantic versioning.

They prevent releases from missing user-facing history, using inconsistent versions, or skipping required checks.

release-changelog — Cursor rule for Cursor by northgraindata: Release rules for the dbt-doctor project, including changelog updates…

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.

agentmods

npx agentmods add rules/northgraindata/dbt-doctor/release-changelog

Clone the repo

git clone --depth 1 https://github.com/northgraindata/dbt-doctor

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/northgraindata/dbt-doctor/release-changelog.svg)](https://agentmods.dev/rules/northgraindata/dbt-doctor/release-changelog)

Your own site

<a href="https://agentmods.dev/rules/northgraindata/dbt-doctor/release-changelog"><img src="https://agentmods.dev/badge/rules/northgraindata/dbt-doctor/release-changelog.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 473 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00473
Opus 5	$0.00000	$0.00236
Sonnet 5	$0.00000	$0.00095
Haiku 4.5	$0.00000	$0.00047

Measured 6d ago against content hash 615a6a1478ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

release-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 6d 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/release-changelog.mdc · 48 lines

What it actually says

Release & CHANGELOG

When preparing a version bump or npm publish, always update the root changelog.

Required files

CHANGELOG.md (repo root) — primary, human-readable history for adopters (Keep a Changelog).
.changeset/*.md — drives semver + per-package changelogs via Changesets.
packages/*/CHANGELOG.md — updated by pnpm changeset version (do not hand-edit unless fixing).

Release workflow

Add a Changeset describing user-facing impact (not implementation detail).
Update CHANGELOG.md under [Unreleased] → move items into [X.Y.Z] - YYYY-MM-DD before tagging.
Run pnpm changeset version then pnpm build && pnpm test.
Commit: chore(release): version packages to X.Y.Z.
Tag with package-scoped tags ([email protected], not vX.Y.Z).
pnpm changeset publish (npm OTP if required).
GitHub release on tag [email protected]; link to root CHANGELOG.md section.

CHANGELOG sections

Use: Added, Changed, Deprecated, Removed, Fixed, Security.

Write for adopters (what changed in behavior), not for maintainers (file names).

Semver

patch — bug fixes, false-positive reductions, docs-only if user-visible.
minor — new rules/features, backward-compatible preset/config changes.
major — breaking CLI/config/API removals or default behavior breaks.

Example entry

## [0.3.1] - 2026-05-31

### Fixed

- SQL style rules skip Jinja in `source()` and `{{ config() }}` blocks.

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.

6d ago First seen · 48 lines · 0 tokens per session scan A 615a6a1478ce

Subscribe to this mod's changes

release-changelog is a cursor rule published in the GitHub repository northgraindata/dbt-doctor (58 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 473 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.

Git and workflow Releases analytics-engineering cli data-engineering data-quality dbt dbt-core

cursorrules

Native SQL extensions for GoldenMatch (D:\showcase\goldenmatch).

benseverndev-oss/goldenmatch · 1,317 tokens

release-notes

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

thatrebeccarae/claude-marketing · 50 tokens

release-changelog