changes
- Repo stars 1,985
- License MIT
- Author updated Live
- Author repo suneditor
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- 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 special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: changes
description: 수동 코드 수정 후 changes.md에 누락된 변경사항 추가 The user has manually modified code and needs changes.md upda…
category: other
runtime: no special runtime
---
# changes output preview
## PART A: Task fit
- Use case: 수동 코드 수정 후 changes.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.) runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “수동 코드 수정 후 changes.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.) runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Start with a small task and check whether the result follows “Decide Fit First / Design Intent / How To Use It”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: changes
description: 수동 코드 수정 후 changes.md에 누락된 변경사항 추가 The user has manually modified code and needs changes.md upda…
category: other
source: JiHong88/suneditor
---
# changes
## When to use
- 수동 코드 수정 후 changes.md에 누락된 변경사항 추가 The user has manually modified code and needs changes.md updated. (When Claude modi…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Decide Fit First / Design Intent / How To Use It” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "changes" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Decide Fit First / Design Intent / How To Use It
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 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:
- Read
prompts/changes-guide.mdfor formatting rules - Run
git diff --stagedandgit diffto find current changes - If no changes found, run
git diff HEAD~1for the last commit - Read the current
changes.md - Analyze the diff — classify each user-facing change as
feat,fix,change, orbreaking - Skip internal-only changes (
style,docs,test,chore,ci,build) - Add new entries to the appropriate section in
changes.md(do not duplicate existing entries) - If unsure about a change's classification, ask before adding
Decide Fit First
Design Intent
How To Use It
Boundaries And Review