You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .agents/skills/macos-release-loopndroll/SKILL.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,10 +32,11 @@ Before releasing, verify:
32
32
## Standard workflow
33
33
34
34
1. Read `package.json` and confirm the current version.
35
-
2. If the user asked for a version bump, edit only `package.json` first. If the user asked to release without specifying a version, bump the patch version in `package.json` by `+0.0.1` first.
36
-
3. Commit and push the version bump before releasing.
37
-
4. Ensure the working tree is clean because `scripts/release-macos.sh` refuses dirty releases unless `ALLOW_DIRTY_RELEASE=true`.
38
-
5. Run:
35
+
2. If the working tree has uncommitted changes, commit and push those changes before changing the version or starting the release. If those changes are not intended for release, stop and confirm with the user instead of releasing them accidentally.
36
+
3. If the user asked for a version bump, edit only `package.json` first. If the user asked to release without specifying a version, bump the patch version in `package.json` by `+0.0.1` first.
37
+
4. Commit and push the version bump before releasing.
38
+
5. Ensure the working tree is clean because `scripts/release-macos.sh` refuses dirty releases unless `ALLOW_DIRTY_RELEASE=true`.
39
+
6. Run:
39
40
40
41
```bash
41
42
bash scripts/release-macos.sh v<version>
@@ -67,6 +68,7 @@ Do not re-implement this unless the script is broken. `scripts/release-macos.sh`
67
68
## Operational guidance
68
69
69
70
- Prefer releasing before making unrelated repo edits. The script expects a clean tree.
71
+
- If there are uncommitted changes in the repo, commit and push them before the version bump and release. Do not ship unreviewed local work by accident; if the changes should not be part of the release, stop and ask the user.
70
72
- If the user does not specify a version, default to the next patch release by bumping `package.json` from the current version to `+0.0.1` before running the release.
71
73
- If you need to add repo changes such as documentation or a skill, do that after the release and commit them separately.
72
74
- If the release already exists for the requested tag, the script will upload the fresh artifacts with `--clobber`.
0 commit comments