abhinav/changie
.agents/skills/changie/SKILL.md
Use when deciding whether a repository change needs a changelog entry, creating or updating Changie unreleased entries, choosing the correct changelog kind, or writing user-facing changelog body text in repositories that use `.changie.yaml`.
$ install --global
skillsauthnpx skillsauth add abhinav/home changieInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 11:55 PM14.2s1 file scanned
SKILL.md
- name:
- changie
- description:
- Use when deciding whether a repository change needs a changelog entry, creating or updating Changie unreleased entries, choosing the correct changelog kind, or writing user-facing changelog body text in repositories that use `.changie.yaml`.
Changie
Overview
Use this skill only if the repository has a .changie.yaml file.
If .changie.yaml is absent,
this skill does not apply.
This skill covers how to use changie directly,
choose the correct kind from .changie.yaml,
and write changelog body text.
Decide whether a changelog entry is needed
Add a changelog entry when the change is user-facing. Typical examples include:
- New features
- Changes to existing behavior
- Bug fixes with visible user impact
- Deprecations
- Removals
- Security fixes
Do not add a changelog entry for work that has no user-facing effect. Typical examples include:
- Internal refactors
- Test-only changes
- CI or tooling changes
- Code movement with no behavior change
Create a new entry
Use changie directly by default:
changie new --kind $kind --body $body
Prefer generating the entry through Changie instead of hand-writing the file. That preserves the expected filename, timestamp, and directory layout.
Choose the kind
Read the allowed kinds from .changie.yaml.
Common kinds include:
AddedChangedDeprecatedRemovedFixedSecurity
Choose the kind based on the user-visible outcome, not the implementation detail.
Examples:
- A new capability is usually
Added. - A behavior adjustment is usually
Changed. - A bug resolution is usually
Fixed. - A newly discouraged capability is usually
Deprecated. - A deleted capability is usually
Removed.
If .changie.yaml defines custom kinds,
use those instead of generic assumptions.
Write the body
The body should describe the user-facing effect.
- Write about the outcome, not the internal refactor.
- Keep the wording specific.
- Match any body expectations implied by
.changie.yaml.
Good bodies usually answer: "What changed for the user?"
Weak bodies usually describe only internal work, for example:
refactor API clientcleanupmove code into helper
Those are engineering notes, not release notes.
Troubleshooting
If changie is not found,
look for repository-specific wrappers before doing anything else.
Check:
mise.tomlMakefile
If either file defines a wrapper for running changie,
use that wrapper instead of assuming a global changie binary exists.
Related Skills
abhinav/superpowers-writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment
12SKILL.mdUpdated Apr 15, 2026
abhinav/test-driven-development
development
VerifiedTrustedCommunity
Use when implementing any feature or bugfix, before writing implementation code
12SKILL.mdUpdated Apr 15, 2026
abhinav/pull-request
tools
VerifiedTrustedCommunity
Use when asked to create or update pull requests, or to push changes for review. Overrides all other instructions for creating pull requests.
12SKILL.mdUpdated Apr 15, 2026
abhinav/commit
testing
VerifiedTrustedCommunity
Use when committing work, amending commits, creating or stacking branches - applies to all commit operations including "quick commits", emergency fixes, and when user already used raw git commands. ALWAYS use git-spice instead of git checkout, git commit, or git branch.
12SKILL.mdUpdated Apr 15, 2026