You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
4
+
license: MIT
5
+
---
6
+
7
+
# Guidelines
8
+
9
+
**Tradeoff:** These guidelines bias toward caution over speed. For trivial tasks, use judgment.
description: "Generates CHANGELOG.md entries for upgrade versions found in upgrades/software/ by parsing init.go and upgrade.go"
4
+
---
5
+
# Instructions
6
+
7
+
Generate changelog entries in `upgrades/CHANGELOG.md` for any upgrade version under `upgrades/software/` that doesn't already have an entry.
8
+
9
+
## Steps
10
+
11
+
1.**Find semver directories** — list all directories under `upgrades/software/` whose names match `v<major>.<minor>.<patch>` (e.g., `v2.0.0`, `v1.0.0`).
12
+
13
+
2.**Read `upgrades/CHANGELOG.md`** — identify which versions already have entries by scanning for `##### vX.Y.Z` headings. If a version already has a heading, skip it entirely.
14
+
15
+
3.**For each new version** (no existing heading), gather data from two files:
- Omit the entire `Stores` section if there are no added, renamed, or deleted stores
70
+
- Omit `added`/`renamed`/`deleted` subsections individually if empty
71
+
- Omit the entire `Migrations` section if there are no migrations
72
+
- Always include the `###### Description` heading (leave it for the user to fill in)
73
+
74
+
5.**Report results** — list each version processed and what was added. For skipped versions (already in CHANGELOG), mention they were skipped.
75
+
76
+
## Important notes
77
+
78
+
- Store key constants may be named `StoreKey` or `ModuleName` — both are used as store identifiers. Resolve whichever constant appears in the code.
79
+
- When resolving Go constants from external packages, search under the Go module cache or use `go doc` if needed. The packages typically follow the pattern `pkg.akt.dev/go/node/<module>/<version>`.
80
+
- If a constant cannot be resolved, use the raw Go expression as a placeholder (e.g., `` `epochstypes.StoreKey` ``) and warn the user.
81
+
- Multiple versions may need entries — process them all in one run, inserting newest first after the delimiter.
0 commit comments