update-changelog/SKILL.md
Record recent changes and decisions in the AGENTS.md file. Use when making project decisions, choosing technologies, establishing conventions, or completing significant changes that should be tracked in the project history.
npx skillsauth add heikopanjas/agent-skills update-changelogInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
After making significant project changes or decisions, record them in the "Recent Updates & Decisions" section at the bottom of AGENTS.md.
Add an entry whenever you:
Each entry starts with a heading containing the date, time, and an optional short label:
### YYYY-MM-DD HH:MM (label)
- Description of change or decision
- Reasoning if non-obvious
- Version bump if applicable
Rules:
YYYY-MM-DDHH:MMVersion bump: X.Y.Z to X.Y.Z (TYPE - reason)The section must be at the end of AGENTS.md. Look for:
## Recent Updates & Decisions
If the section does not exist, create it by appending the following to the bottom of AGENTS.md:
---
## Recent Updates & Decisions
Then add the new entry below the heading.
Also update the Last updated timestamp near the top of AGENTS.md to today's date.
## Recent Updates & Decisions
### 2026-02-25 14:30 (anyhow migration)
- Migrated error handling from custom Result type alias to anyhow crate
- lib.rs now re-exports pub use anyhow::Result
- Replaced all Err(format!(...).into()) with Err(anyhow!(...))
- Version bump: 9.0.2 to 9.0.3 (PATCH - internal refactor)
### 2026-02-24 09:15 (v9.0.0)
- MAJOR version bump: 8.0.0 to 9.0.0 (V1 removed, V3 template format)
- Removed V1 template engine and all V1 templates
- Introduced V3 template format with shared file groups and includes
development
Swift coding conventions and best practices for modern Swift development. Use when writing, reviewing, or refactoring Swift code to ensure consistency with naming conventions, access control, async/await patterns, and SwiftUI/framework best practices.
development
Determine whether a version bump is required after code changes and apply semantic versioning (SemVer). Use when making code changes, fixing bugs, adding features, or introducing breaking changes to a project that uses SemVer.
development
Rust coding conventions and best practices for idiomatic Rust development. Use when writing, reviewing, or refactoring Rust code to ensure consistency with error handling, RAII principles, naming conventions, and Rust edition best practices.
development
Commit specific staged changes to a git repository using conventional commits format. Use when the user asks to commit, stage, or check in particular files or changes.