changes

Other Community

Skill notes

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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
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.

Author source file SKILL.md

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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.