Change
SkillDev toolsChange writes the documentation developers need when your software changes, so breaking changes never come as a surprise. Once added, your AI can produce changelogs, deprecation notices, and migration guides on request. It is useful whenever you need release notes, a sunset timeline, or a step-by-step migration path.
Use Change in Claude, ChatGPT or Ahel Desktop
Free. Sign in, add Change and connect your AI. About a minute.
Also: Claude Code · Cursor · Codex
Then ask your AI: use the Change skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
After adding Change, ask your AI to "write the changelog" or "document this breaking change" to get started.
What your AI can do with it
- Write changelogs for new releases
- Draft deprecation notices
- Create step-by-step migration guides
- Build sunset timelines for retiring features
- Write release notes
- Document breaking changes clearly
What this skill tells your AI
The instructions your AI receives, as published by linzhe001/harness-research in .agents/skills/change/SKILL.md and read by Ahel’s review.
Use $change for: Classify a mature-codebase delta and execute only the owning route.
Runtime Contract
- Read
harness_core/recipes/change.yamland identify the current Action. - Resolve Capability Packs from that Action plus the active Assurance Profile.
- Load only the resolved Packs. Ordinary Actions allow 3; declared high-risk Actions allow 5 and must record the escalation reason.
- Execute, validate postconditions, and record semantic Runtime Events and Gate Evidence. Do not infer success from artifact existence.
- After durable changes under
docs/, runpython tooling/harness.py docs sync --json; this establishes or validates the live docs link. Git hooks only repair the link after checkout, merge, commit, or rewrite. - Pause only at a declared interrupt or human-stop boundary.
Actions:
change.classify:build-and-change,policy-and-approvalchange.execute:build-and-change,policy-and-approval
Default profile: reproducible.
Start interactively with python tooling/harness.py change --json; use --auto for a bounded fresh Agent per Action.
Inspect with python tooling/harness.py status --json. Legacy internal
sources are inactive migration/debug references, not normal routes.
Signals
- GitHub stars
- 87
- Forks
- 10
- Last commit
- Aug 2026
Advanced
- Item type
- skill
- Key
change- Source
- github.com/linzhe001/harness-research
github.com/linzhe001/harness-research