Individual skill
changesets
Concise PR finalization changesets. Use when implementation scope is complete and focused validation has finished to classify release impact, consolidate the PR's existing changeset, or write its consumer release note.
repos/effect/.agents/skills/changesets/SKILL.md
Source commit a471adb24d750ab9e8d8312edad53ff6f26d961b
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,214
- Repository last updated
- Nov 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,748 bytesSKILL.mdcore · 3,748 bytesSKILL.mdcore · 3,748 bytesauthoring.mddoc · 2,470 bytes
Read excerpt
Treat a changeset as the release note for the complete PR, not as a log of work
performed along the way. Finalize it after the current implementation scope and
focused validation are complete.
## Workflow
1. Inspect the complete diff from the merge base, including changeset files
already introduced by the PR, and identify directly affected published
packages.
2. Classify impact across source types, runtime behavior, entrypoints, required
services, lifecycle, and persisted or wire data.
3. Perform the breaking audit below.
4. Record a reason no changeset is required, or update the PR's existing
changeset. Create one only when the PR does not have one. When required, read