@detergent-software/conductor 3.6.1-dev.1 → 3.7.0-dev.1

package/plugin/skills/work-item/SKILL.md

@@ -26,6 +26,7 @@ This skill is the order of work. **Conductor does the rest**: every read and wri
 | Branch, ahead/behind, dirty files, the branch's PR, other repos' checkouts | `conduct state` |
 | Rename the branch; clone another repo | `conduct branch <type> <slug>`; `conduct checkout <owner>/<repo> <type> <slug>` |
 | The plan's landing mode | `conduct mode --tier <S\|M\|L> --files <a,b>` |
+| Run the profile's checks for what the branch changes, PASS/FAIL, recorded on the worker | `conduct checks [--all] [--json]` |
 | Open the PR; read its threads; answer one | `conduct pr create …`; `conduct pr threads <pr>`; `conduct reply <pr> [<thread>] --body-file <file>` |
 | Abandon the item's PR (closed unmerged, with a note saying why) | `conduct pr abandon <pr> --reason "…" [--force]` |
 | Stop the item's work for good (back to not-started, labelled human) | a `<skill> · Shelved` note with `conduct note` (Rules: stopping for good) |
@@ -49,7 +50,7 @@ Below, `KEY-n` is an item key with the profile's key prefix, `<skill>` is the wo
 |---|---|
 | `rules` | Throughout: the project's own rules (what never to touch, what a verify run refuses). Read at the start. |
 | `orient` | Orient: what else to read, and what the Started note carries. |
-| `checks` | Verify: the checks for each area the diff touches. |
+| `checks` | Verify: the checks for each area the diff touches that the profile's `checks` don't run (all of them for a profile with none). |
 | `verify` | Verify: how the live proof runs (the verify skill's surfaces, locks, the evidence path). |
 | `pr` | PR: what goes out alongside the PR (assets published elsewhere, other PRs). |
 | `after-merge` | Land: after the pipelines settle (staged releases, follow-up PRs). |
@@ -218,7 +219,7 @@ Throughout:
 
 ## 6. Verify
 
-Run every check the `checks` hook names for each area the diff touches (`git diff --stat origin/<base>...`).
+Run `conduct checks` in the background (`run_in_background`: a build and a test suite can outlast a shell call's timeout), and read its output when it exits: it runs the checks the profile declares for the paths the branch changes, committed or not, one after another, and prints a PASS or FAIL line for each, with the end of a failure's output under it. It exits 1 when one failed, and records the verdicts on the worker. Fix a failure and run it again. Then run whatever the `checks` hook names for each area the diff touches (`git diff --stat origin/<base>...`) that `conduct checks` didn't run. When the profile declares no checks, `conduct checks` refuses and says so, and the hook names them all.
 
 Then: