@sassywares/skills 0.7.0 → 0.7.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/package.json
CHANGED
|
@@ -41,11 +41,13 @@ Snapshot the PR state first, then act in this order:
|
|
|
41
41
|
|
|
42
42
|
1. **Terminal** — `MERGED`/`CLOSED` → if it is `MERGED` and `after_merge` resolves for this PR's head, run those hooks once (see Step 3) before stopping.
|
|
43
43
|
2. **Capture the head SHA** — a later push invalidates this snapshot's CI.
|
|
44
|
-
3. **Feedback before CI** — fetch open review threads (`gh pr view --json reviewThreads,comments`).
|
|
44
|
+
3. **Feedback before CI** — fetch open review threads (`gh pr view --json reviewThreads,comments`). Fix every actionable thread (see **Fixing** below), then reply on each with what changed and the commit. A thread that is not actionable gets a reply saying why. Never wait for a reviewer who is "still reviewing" before acting on feedback already posted.
|
|
45
45
|
4. **Stale-SHA cancellation** — if the head moved since step 2, skip the CI work for this snapshot.
|
|
46
|
-
5. **CI** — `gh pr checks`. One pass for all failures. Flaky/infra → `gh run rerun <run-id> --failed`. Real failure → fix it (
|
|
46
|
+
5. **CI** — `gh pr checks`. One pass for all failures. Flaky/infra → `gh run rerun <run-id> --failed`. Real failure → fix it (see **Fixing**). Mark each check handled; unfixed checks stay red.
|
|
47
47
|
6. **Branch currency** — if the branch is `BEHIND` or `DIRTY`, update it (`gh pr update-branch <ref>`, or ask for a local rebase). Do not update just because the base moved; only when the status actually requires it.
|
|
48
48
|
|
|
49
|
+
**Fixing.** Load the `sassy-cycle` skill on rework with the threads and failing checks as findings and the PR's changed files as the scope hint; it fixes and verifies, at most two passes. Then load `sassy-commit` with `branch:current` and `git push`. A finding the cycle leaves open, or a failure you cannot diagnose from the log and the diff, is `needs-human`. Never load `sassy-debug` or `sassy-ship` from here — they commit, open PRs, and babysit on their own, which nests a second watch over this PR.
|
|
50
|
+
|
|
49
51
|
After a tick with no true stop, wait and run the next tick. Checkpoint mode: run one tick and report paused with the resume command.
|
|
50
52
|
|
|
51
53
|
## Step 3 — Stop conditions
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: sassy-commit-push-pr
|
|
3
3
|
description: >-
|
|
4
4
|
Commit, push, and open a PR, then babysit it by default. Use when asked to
|
|
5
|
-
|
|
5
|
+
open or update a PR, or for a PR-description-only flow (writing, rewriting, or
|
|
6
6
|
describing a PR body).
|
|
7
7
|
argument-hint: "[PR ref] [branch:new|current] [base:<branch>] [babysit:on|off] [checkpoint] [merge:on|off] [delete-branch:on|off]"
|
|
8
8
|
disable-model-invocation: true
|
|
@@ -13,7 +13,7 @@ disable-model-invocation: true
|
|
|
13
13
|
|
|
14
14
|
**Outcome:** a grounding brief on disk for the area you asked about, and a 3–5 line gist back in this context. Nothing else.
|
|
15
15
|
|
|
16
|
-
**Orchestrator only.** Do not read the repo yourself. One `scout` dispatch per
|
|
16
|
+
**Orchestrator only.** Do not read the repo yourself. One `scout` dispatch per run: the brief is one file per worktree, so a second scout replaces the first one's brief. When several areas matter, scope them into that one dispatch.
|
|
17
17
|
|
|
18
18
|
**Harness.** Loading another skill, dispatching an agent, and any command you hand the user follow the `sassy-setup` skill's `references/harness.md`. Read it once per run, before the first of those.
|
|
19
19
|
|
|
@@ -26,7 +26,7 @@ disable-model-invocation: true
|
|
|
26
26
|
|
|
27
27
|
## Workflow
|
|
28
28
|
|
|
29
|
-
1. **Scope.** Reduce the request to
|
|
29
|
+
1. **Scope.** Reduce the request to the question the brief will answer, in one line — naming every area downstream needs, since there is only one brief.
|
|
30
30
|
2. **Dispatch `scout`** with that scope, what the caller intends to do with it, and the paths or areas you already suspect. The brief also carries matching docs from the project's knowledge paths (`knowledge.read` in `.sassywares/config.yaml`, nearest walking up) — pass that section on to the caller rather than dropping it.
|
|
31
31
|
3. **Keep the gist.** Read the returned gist; do not pull the brief's bulk into this context.
|
|
32
32
|
4. **Report the brief path** to the caller, so downstream agents read it instead of scouting again.
|
|
@@ -50,7 +50,7 @@ It is fresh only while its `head` and `dirty` lines match the working tree. Afte
|
|
|
50
50
|
|
|
51
51
|
| Rule | Requirement |
|
|
52
52
|
|------|-------------|
|
|
53
|
-
| One
|
|
53
|
+
| One brief | One dispatch, one brief per worktree. Cover every area the work needs in its scope; never run scouts side by side. |
|
|
54
54
|
| Gist only | Return the gist and the brief path. Never paste the brief. |
|
|
55
55
|
| No edits | Scouting is read-only. It never changes code or commits. |
|
|
56
56
|
| Learnings are listed, not judged | Prior learnings come back as path and title. The consumer decides whether one applies; scout never ranks or recommends them. |
|
|
@@ -54,7 +54,7 @@ Ask which one, unless the request already made it obvious. The answer changes th
|
|
|
54
54
|
|
|
55
55
|
| Location | Path | Who gets it | Extra work |
|
|
56
56
|
|---|---|---|---|
|
|
57
|
-
| **Internal** — part of this suite | `skills/<name>/` in the sassy-skills repo | Everyone, once pushed to `main` | Name it `sassy-<name>`, run `scripts/sync.sh` — it
|
|
57
|
+
| **Internal** — part of this suite | `skills/<name>/` in the sassy-skills repo | Everyone, once pushed to `main` | Name it `sassy-<name>`, bump the minor version by hand (a new skill), then run `scripts/sync.sh` — it commits, tags, and publishes; edits to an existing skill take its automatic patch bump |
|
|
58
58
|
| **Project** — team workflow | `<repo>/.agents/skills/<name>/` | Everyone who clones that repo | Commit it; prefix the project (`tap2-…`) so it can't collide with a suite skill or a harness built-in |
|
|
59
59
|
| **User** — personal workflow | `~/.agents/skills/<name>/` | Only this person, every repo on this machine | None — but nothing gates it either; never put something a teammate needs here |
|
|
60
60
|
|
|
@@ -41,7 +41,7 @@ Plain English, no filler. Where the skill returns a result, give the shape of th
|
|
|
41
41
|
|
|
42
42
|
## 5. Place and install
|
|
43
43
|
|
|
44
|
-
- **Internal:** `skills/<name>/` in the sassy-skills repo, named `sassy-<name>`; then `scripts/sync.sh` — it commits,
|
|
44
|
+
- **Internal:** `skills/<name>/` in the sassy-skills repo, named `sassy-<name>`; link it globally as that repo's `AGENTS.md` describes, bump the minor version by hand (a new skill is a minor release), then run `scripts/sync.sh` — it commits, tags, and publishes. Say that this ships to everyone before you do it.
|
|
45
45
|
- **Project:** `<repo>/.agents/skills/<name>/`, prefixed with the project so it cannot collide with a suite skill or a harness built-in; then commit it.
|
|
46
46
|
- **User:** `~/.agents/skills/<name>/` (plus a `~/.claude/skills/<name>` link for Claude Code). Nothing gates it, so check it actually works before trusting it.
|
|
47
47
|
|