@sassywares/skills 0.6.0 → 0.6.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CONCEPTS.md CHANGED
@@ -58,7 +58,7 @@ A settled in-context brief produced by `sassy-plan` when the user picks "start w
58
58
 
59
59
  ## Handoff
60
60
 
61
- `sassy-handoff` writes a self-contained handoff file under `/tmp/sassy-handoff-<uid>/<harness>/` and gives the user its path and a paste-ready prompt. A skill cannot start a session, so the user opens the fresh one; the file is the only bridge, in any harness.
61
+ `sassy-handoff` writes a self-contained handoff file under `/tmp/sassywares/<harness>/handoffs/` and gives the user its path and a paste-ready prompt. A skill cannot start a session, so the user opens the fresh one; the file is the only bridge, in any harness.
62
62
 
63
63
  ## Sync
64
64
 
package/README.md CHANGED
@@ -85,7 +85,7 @@ Debugging:
85
85
  | **`sassy-lfg`** | Executes every phase of a plan, or one in-context brief, then closes out via `sassy-ship` after code approval. |
86
86
  | **`sassy-cycle`** | Runs one unit of work through implement → review → validate → fix → re-check. |
87
87
  | **`sassy-debug`** | Diagnoses a bug, gates the fix, fixes via `sassy-cycle`, then ships after code approval. Debug takes no mode and always leaves ship's review gate in place unless you invoke ship yourself with `mode:auto`. |
88
- | **`sassy-handoff`** | Writes a self-contained handoff file to a temp directory and gives you its path plus a one-line prompt to paste into a fresh session, in any harness. |
88
+ | **`sassy-handoff`** | Writes a self-contained handoff file to `/tmp/sassywares/<harness>/handoffs/` and gives you its path plus a one-line prompt to paste into a fresh session, in any harness. |
89
89
 
90
90
  ### Code quality
91
91
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@sassywares/skills",
3
- "version": "0.6.0",
3
+ "version": "0.6.1",
4
4
  "description": "Lean, explicit-invocation Agent Skills for shipping fast: plan, work, review, validate, ship.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -54,7 +54,7 @@ Treat the reads as a snapshot; re-read branch and staged set right before commit
54
54
  5. **Message** — imperative subject naming the outcome, not the file list. Body only when the motivation is not obvious.
55
55
  - Bad: `Update checkout.rb`
56
56
  - Good: `Fix double-submit on checkout`
57
- 6. **Stage and commit** — stage **named files only** (never `git add -A` or `git add .`). Write the full message to a file outside the repo, then:
57
+ 6. **Stage and commit** — stage **named files only** (never `git add -A` or `git add .`). Write the full message to `/tmp/sassywares/<harness>/commits/<UTC timestamp>-<slug>.txt` (directory per the `sassy-setup` skill's `references/harness.md`), then:
58
58
  ```
59
59
  git add file1 file2 file3
60
60
  git commit -F <message-file> -- file1 file2 file3
@@ -57,6 +57,6 @@ Only an exit-0 empty list means "no open PR". A non-zero exit means **unknown**
57
57
  - Title: outcome-stating, concise.
58
58
  - Body: what changed, why, and how it was verified. Preserve any existing `Related:` / `Fixes` line on an update.
59
59
  - If no PR exists, compose fresh; if one does, edit its body.
60
- 6. **Apply** — re-check PR presence. With a matching PR: `gh pr edit <url> --body-file <path>`. With none: `gh pr create --base <base> --title <title> --body-file <path>`. Always pass the body via `--body-file`, never stdin, and always name the base.
60
+ 6. **Apply** — re-check PR presence. With a matching PR: `gh pr edit <url> --body-file <path>`. With none: `gh pr create --base <base> --title <title> --body-file <path>`. Always pass the body via `--body-file`, never stdin, and always name the base. The body file lives in `/tmp/sassywares/<harness>/prs/` (per `references/harness.md`), named `<UTC timestamp>-<branch>.md`.
61
61
  7. **`after_create` hooks.** Only when this run **created** the PR — an update does not fire them, say so in one line. Same resolution and ordering as step 2, with the PR URL added to the brief. These must leave the tree clean: anything they write is reported, not committed.
62
62
  8. **Babysit** — with `babysit:on` (default), load `sassy-babysit` and follow it for the PR just opened or updated, forwarding `checkpoint`, `merge:`, and `delete-branch:` unchanged. Report the PR URL and the babysit status; for a continuous watch beyond this run, point the user at `sassy-babysit`. With `babysit:off`, report the PR URL only.
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  name: sassy-handoff
3
3
  description: >-
4
- Write a self-contained handoff file to a temp directory so a fresh session —
4
+ Write a self-contained handoff file under /tmp/sassywares so a fresh session —
5
5
  in any harness — can continue the work, then give the user its path and a
6
6
  one-line prompt to paste. Use at a phase boundary, when context is getting
7
7
  long, or when the user asks to hand off.
@@ -28,12 +28,9 @@ disable-model-invocation: true
28
28
  - Confirm nothing that matters exists only in this conversation.
29
29
  - Redact secrets, credentials, and unrelated personal data.
30
30
 
31
- 3. **Write the file.** One file per handoff, under the harness's handoff directory:
31
+ 3. **Write the file.** One file per handoff, in `/tmp/sassywares/<harness>/handoffs/` — create the directory with the `references/harness.md` snippet, `<purpose>` = `handoffs`:
32
32
 
33
33
  ```bash
34
- DIR="/tmp/sassy-handoff-$(id -u)/<harness>" # pi, claude, … — the harness you are running in
35
- [ -L "/tmp/sassy-handoff-$(id -u)" ] && { echo "unsafe symlink" >&2; exit 1; }
36
- (umask 077; mkdir -p "$DIR")
37
34
  FILE="$DIR/$(date -u +%Y%m%dT%H%M%SZ)-<kebab-goal>.md"
38
35
  ```
39
36
 
@@ -76,6 +73,6 @@ disable-model-invocation: true
76
73
 
77
74
  - **Pointer-first.** Name the plan path, phase, key files, and decisions rather than reproducing them. The plan is the source of truth; the file points at it.
78
75
  - **Self-contained.** The fresh session cannot see this conversation. When there is no plan file, the brief goes in the handoff file in full.
79
- - **Outside the repo.** The file lives in the temp directory only — never committed, never inside the working tree. `/tmp` clearing on reboot is the intended lifetime.
76
+ - **Outside the repo.** The file lives under `/tmp/sassywares/` only — never committed, never inside the working tree. `/tmp` clearing on reboot is the intended lifetime.
80
77
  - **Do not invent a continuation.** If the next step is a real fork with mutually exclusive options, list them under **Next steps**; do not silently pick.
81
78
  - **The skill does not switch sessions.** Never claim it did; the user starts the fresh session.
@@ -33,10 +33,12 @@ disable-model-invocation: true
33
33
 
34
34
  ## The brief
35
35
 
36
- The scout writes it under a per-user temp directory, keyed by the worktree root:
36
+ The scout writes it under `/tmp/sassywares/<harness>/grounding/` (see `references/harness.md` in the `sassy-setup` skill), keyed by the worktree root:
37
37
 
38
38
  ```bash
39
- ROOT="/tmp/sassy-grounding-$(id -u)"
39
+ SW=/tmp/sassywares
40
+ HARNESS="${SASSY_HARNESS:-$(if [ -n "${CLAUDECODE:-}" ]; then echo claude; elif [ -n "${PI_CODING_AGENT:-}" ]; then echo pi; else echo other; fi)}"
41
+ ROOT="$SW/$HARNESS/grounding"
40
42
  ROOT_ABS=$(cd "$(git rev-parse --show-toplevel 2>/dev/null || echo "$PWD")" && pwd -P)
41
43
  KEY=$(printf '%s' "$ROOT_ABS" | shasum -a 256 | cut -d' ' -f1)
42
44
  BRIEF="$ROOT/$KEY.md"
@@ -66,7 +66,7 @@ A check run never edits the config and never rewrites the tree: it prints what `
66
66
  **Installed** means all four `<name>.md` files exist in the user scope or the project scope. If they do, report which scope and move on. If any are missing, ask once where to install, recommending user scope:
67
67
 
68
68
  - **User scope** — every project on this machine, updated by `git pull`. Reuse the user's sassy-agents checkout if they have one; otherwise ask where to clone it (`git clone https://github.com/sassywares/sassy-agents.git <dir>`). Then run `<dir>/scripts/install.sh <folder>`, which symlinks the folder into the user scope and never overwrites a differing file.
69
- - **Project scope** — only this project, pinned with it. Shallow-clone into a temp directory, copy `<folder>/*.md` into the project scope directory, delete the clone. Never overwrite an existing agent file that differs: show it and ask. The copies join step 8's commit list.
69
+ - **Project scope** — only this project, pinned with it. Shallow-clone into `/tmp/sassywares/<harness>/scratch/` (per `references/harness.md`), copy `<folder>/*.md` into the project scope directory, delete the clone. Never overwrite an existing agent file that differs: show it and ask. The copies join step 8's commit list.
70
70
 
71
71
  - **Tell the user to `/reload`** (or restart the harness). The skills and agents are invisible to the harness until it rescans.
72
72
 
@@ -30,4 +30,23 @@ For any other harness, give the skill name and its arguments and let the user in
30
30
 
31
31
  ## Temp files
32
32
 
33
- Per-user temp files live under `/tmp/sassy-<purpose>-$(id -u)/`, created `0700`, never inside the repo. A symlinked root aborts rather than being followed. Two use it today: the grounding brief (`/tmp/sassy-grounding-<uid>/`, written by `scout`) and handoff files (`/tmp/sassy-handoff-<uid>/<harness>/`, written by `sassy-handoff`).
33
+ Every file a skill or agent writes outside the repo goes under **`/tmp/sassywares/<harness>/<purpose>/`** — never loose in `/tmp`, never inside the working tree. Each harness gets its own folder; the harness is detected from its environment (`CLAUDECODE` → `claude`, `PI_CODING_AGENT` → `pi`, else `other`), and `SASSY_HARNESS` overrides it. Directories are `0700`; a symlinked directory, or a `/tmp/sassywares` owned by someone else, aborts rather than being followed.
34
+
35
+ ```bash
36
+ SW=/tmp/sassywares
37
+ HARNESS="${SASSY_HARNESS:-$(if [ -n "${CLAUDECODE:-}" ]; then echo claude; elif [ -n "${PI_CODING_AGENT:-}" ]; then echo pi; else echo other; fi)}"
38
+ DIR="$SW/$HARNESS/<purpose>"
39
+ for d in "$SW" "$SW/$HARNESS" "$DIR"; do [ -L "$d" ] && { echo "unsafe symlink: $d" >&2; exit 1; }; done
40
+ (umask 077; mkdir -p "$DIR")
41
+ [ -O "$SW" ] || { echo "not owned by you: $SW" >&2; exit 1; }
42
+ ```
43
+
44
+ | Purpose | Folder | Written by |
45
+ |---|---|---|
46
+ | Grounding briefs | `grounding/` | `scout` (read by every agent) |
47
+ | Handoff files | `handoffs/` | `sassy-handoff` |
48
+ | Commit messages | `commits/` | `sassy-commit` |
49
+ | PR bodies | `prs/` | `sassy-commit-push-pr` |
50
+ | Anything else — clones, captured output, drafts | `scratch/` | any skill or agent |
51
+
52
+ Name files so a run can find its own: a UTC timestamp plus a short slug (`20261027T101500Z-fix-checkout.txt`). Delete scratch you no longer need; `/tmp` clearing on reboot covers the rest. A new purpose gets a new row here, not a new top-level folder.