@brainervirus/workit-claude-code 8.44.3 → 8.45.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brainervirus/workit-claude-code",
-  "version": "8.44.3",
+  "version": "8.45.1",
   "private": false,
   "description": "Workit Claude Code plugin — session and per-turn task context, branch policy on git shell commands, workit method skills, and verifier/reviewer/implementer agents",
   "keywords": [
@@ -39,8 +39,8 @@
     "build": "bun scripts/build.ts"
   },
   "devDependencies": {
-    "@brainervirus/workit-cli": "^8.44.3",
-    "@brainervirus/workit-core": "^8.44.3"
+    "@brainervirus/workit-cli": "^8.45.1",
+    "@brainervirus/workit-core": "^8.45.1"
   },
   "engines": {
     "node": ">=24"

package/skills/implement/SKILL.md

@@ -30,7 +30,7 @@ description: Build a requested change in small verified steps - follow local pat
    change a screenshot or console/network check (chrome devtools or
    agent-browser), an API a quoted real response. App not runnable? Say so
    plainly, never claim success.
-6. Commit: `workit git commit -m "<type>: <what>" -- <paths>` (or `--all`).
+6. Commit: `workit git commit -m "<type>: <what>" -- <paths>` (or `--all`). One file holding two changes: stage one change's hunks with `workit git stage --patch <file>` (a `git diff -- <file>` cut to them), then `workit git commit -m "<msg>" --staged` (exactly the index); a path staged in part commits only its staged hunks (`--whole` takes the file).
    No endpoint named? Stop here and state the next command. Hand delivery to
    ship, which pushes and opens the PR with its body shape (call the Skill tool with `workit:ship`), only
    when that was requested, or the request implies delivery and the effective

package/skills/ship/SKILL.md

@@ -49,7 +49,7 @@ the same check. Fix round and recheck both failed: a decider (call the Skill too
 5. **CI.** Local gates mirror CI: push and continue; `workit ci wait` once on
    the final head, in the background where the host allows. Red: read `logTail`, classify. Flake or infra: one
    `workit ci rerun --failed --reason flake|infra` per head. Real: reproduce
-   with `workit check`, fix the root cause, batch every fix in one push. A tool warning is a finding: fix it in this PR in the right layer, or record the false positive with evidence; pre-existing ones get their own PR.
+   with `workit check`, fix the root cause, batch every fix in one push, one focused commit per fix (unrelated hunks in one file: `workit git stage --patch <file>`, then `workit git commit -m "<msg>" --staged`). A tool warning is a finding: fix it in this PR in the right layer, or record the false positive with evidence; pre-existing ones get their own PR.
 6. **Verified.** The lane in `workit pr status` decides: none, no verdict; self, your `--self` verdict; focused or full (or `verification: self|independent`), one non-author verifier per PR after the last push, never per push (call the Skill tool with `workit:review`), on Claude Code with the `model` and `effort` of `workit models show --role verifier`. A docs-only push (or test-only under a unit verdict) keeps the verdict (`carried`); `reverify: focused` re-checks only the new diff, reusing green CI; one verdict at a stack's top covers its unchanged lower PRs. Land only when
    granted: `workit stack land` or `workit pr merge`; `--unverified --reason` if user-asked.
    Never pipe a delivery verb through `grep`: read its exit code, or use `--json`.