changes
- Repo stars 1,985
- License MIT
- Author repo suneditor
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 94 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @JiHong88 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
The user has manually modified code and needs `changes.md` updated.
(When Claude modifies code, `changes.md` is updated automatically per CLAUDE.md instructions. This skill is only for user-initiated changes.)
Follow the rules defined in `prompts/changes-guide.md` exactly.
Steps:
1. Read `prompts/changes-guide.md` for formatting rules
2. Run `git diff --staged` and `git diff` to find current changes
3. If no changes found, run `git diff HEAD~1` for the last commit
4. Read the current `changes.md`
5. Analyze the diff — classify each user-facing change as `feat`, `fix`, `change`, or `breaking`
6. Skip internal-only changes (`style`, `docs`, `test`, `chore`, `ci`, `build`)
7. Add new entries to the appropriate section in `changes.md` (do not duplicate existing entries)
8. If unsure about a change's classification, ask before adding
Sections and files
Listed in source order.
sections -> → →
terms -> The user has manually modified code and needs changes.md updated. · Follow the rules defined in prompts/changes-guide.md exactly. · Steps: 1.
files/cmd -> changes.md · prompts/changes-guide.md · git diff --staged · git diff · git diff HEAD~1 · feat · fix · change
body sha256 -> 3d1eb50dcdfc
The user has manually modified code and needs
changes.mdupdated. (When Claude modifies code,changes.mdis updated automatically per CLAUDE.md instructions. This skill is only for user-initiated changes.)Follow the rules defined in
prompts/changes-guide.mdexactly.Steps: 1. Read
prompts/changes-guide.mdfor formatting rules 2. Rungit diff --stagedandgit diffto find current changes 3. If no changes found, rungit diff HEAD~1for the last commit 4. Read the currentchanges.md5. Analyze the diff — classify each user-facing change asfeat,fix,change, orbreaking6. Skip internal-only changes (style,docs,test,chore,ci,build) 7. Add new entries to the appropriate section inchanges.md(do not duplicate existing entries) 8. If unsure about a change's classification, ask before adding