geneseed 3.11.0 → 3.13.0

package/src/loops/ci-repair.json

@@ -0,0 +1,19 @@
+{
+  "name": "ci-repair",
+  "description": "Read the branch's failing CI checks, fix one code failure per iteration, test, and push, until CI is green or only flaky or infra failures remain.",
+  "category": "day-to-day",
+  "nodes": ["ci-triage", "ci-fix", "test"],
+  "start": "ci-triage",
+  "edges": [
+    { "from": "ci-triage", "on": "more", "to": "ci-fix" },
+    { "from": "ci-triage", "on": "done", "to": "$close" },
+    { "from": "ci-fix", "on": "pass", "to": "test" },
+    { "from": "ci-fix", "on": "fail", "to": "$stop" },
+    { "from": "test", "on": "pass", "to": "ci-triage" },
+    { "from": "test", "on": "fail", "to": "ci-fix" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["ci-triage", "ci-fix", "test"], "max": 10, "iteration": true },
+    { "name": "fix-test", "nodes": ["ci-fix", "test"], "max": 3 }
+  ]
+}

package/src/loops/deps-upgrade.json

@@ -0,0 +1,29 @@
+{
+  "name": "deps-upgrade",
+  "description": "Confirm the suite is green, then upgrade one package or group per iteration: read its breaking changes, bump and adapt, test, audit, and review, until every named package is upgraded.",
+  "category": "day-to-day",
+  "rules": [
+    "The card's write set names the manifest, the lockfile and every file the bump adapts."
+  ],
+  "nodes": ["baseline-green", "upgrade-scout", "apply", "test", "deps-audit", "review"],
+  "start": "baseline-green",
+  "edges": [
+    { "from": "baseline-green", "on": "pass", "to": "upgrade-scout" },
+    { "from": "baseline-green", "on": "fail", "to": "$stop" },
+    { "from": "upgrade-scout", "on": "more", "to": "apply" },
+    { "from": "upgrade-scout", "on": "done", "to": "$close" },
+    { "from": "apply", "on": "pass", "to": "test" },
+    { "from": "test", "on": "pass", "to": "deps-audit" },
+    { "from": "test", "on": "fail", "to": "apply" },
+    { "from": "deps-audit", "on": "pass", "to": "review" },
+    { "from": "deps-audit", "on": "fail", "to": "apply" },
+    { "from": "review", "on": "pass", "to": "upgrade-scout" },
+    { "from": "review", "on": "fail", "to": "apply" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["upgrade-scout", "apply", "test", "deps-audit", "review"], "max": 20, "iteration": true },
+    { "name": "apply-test", "nodes": ["apply", "test"], "max": 5 },
+    { "name": "review-fix", "nodes": ["apply", "test", "deps-audit", "review"], "max": 3 }
+  ],
+  "ignoreDeletions": ["**/package-lock.json", "**/yarn.lock", "**/pnpm-lock.yaml", "**/*.lock", "**/gradle.lockfile"]
+}

package/src/loops/enforce-architecture-rule.json

@@ -0,0 +1,28 @@
+{
+  "name": "enforce-architecture-rule",
+  "description": "Confirm the suite is green, encode the requirement's architecture rule as a test with an allowlist of today's violations for the user to review, then fix one violation per iteration, test, and review, until the allowlist is empty.",
+  "category": "architecture",
+  "rules": [
+    "Each fix removes its violation's allowlist entry in the same iteration."
+  ],
+  "nodes": ["baseline-green", "fitness-define", "identify", "apply", "test", "review"],
+  "start": "baseline-green",
+  "edges": [
+    { "from": "baseline-green", "on": "pass", "to": "fitness-define" },
+    { "from": "baseline-green", "on": "fail", "to": "$stop" },
+    { "from": "fitness-define", "on": "pass", "to": "identify" },
+    { "from": "fitness-define", "on": "fail", "to": "$stop" },
+    { "from": "identify", "on": "more", "to": "apply" },
+    { "from": "identify", "on": "done", "to": "$close" },
+    { "from": "apply", "on": "pass", "to": "test" },
+    { "from": "test", "on": "pass", "to": "review" },
+    { "from": "test", "on": "fail", "to": "apply" },
+    { "from": "review", "on": "pass", "to": "identify" },
+    { "from": "review", "on": "fail", "to": "apply" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "apply", "test", "review"], "max": 20, "iteration": true },
+    { "name": "apply-test", "nodes": ["apply", "test"], "max": 5 },
+    { "name": "review-fix", "nodes": ["apply", "test", "review"], "max": 3 }
+  ]
+}

package/src/loops/feature.json

@@ -0,0 +1,24 @@
+{
+  "name": "feature",
+  "description": "Plan the feature into ordered iterations, then build each one: apply, test, and review, until the plan is complete — and an independent done-check maps every requirement to a passing test before the loop closes.",
+  "category": "development",
+  "nodes": ["plan", "identify", "apply", "test", "review", "done-check"],
+  "start": "plan",
+  "edges": [
+    { "from": "plan", "on": "pass", "to": "identify" },
+    { "from": "identify", "on": "more", "to": "apply" },
+    { "from": "identify", "on": "done", "to": "done-check" },
+    { "from": "apply", "on": "pass", "to": "test" },
+    { "from": "test", "on": "pass", "to": "review" },
+    { "from": "test", "on": "fail", "to": "apply" },
+    { "from": "review", "on": "pass", "to": "identify" },
+    { "from": "review", "on": "fail", "to": "apply" },
+    { "from": "done-check", "on": "pass", "to": "$close" },
+    { "from": "done-check", "on": "fail", "to": "identify" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "apply", "test", "review", "done-check"], "max": 20, "iteration": true },
+    { "name": "apply-test", "nodes": ["apply", "test"], "max": 5 },
+    { "name": "review-fix", "nodes": ["apply", "test", "review"], "max": 3 }
+  ]
+}

package/src/loops/fix-flaky-tests.json

@@ -0,0 +1,30 @@
+{
+  "name": "fix-flaky-tests",
+  "description": "Confirm the suspected flaky tests by 20 repeated runs, then fix one per iteration at its root cause, re-confirm it with 20 runs, test, and review.",
+  "category": "tests",
+  "rules": [
+    "Fix at the root cause — shared state, ordering, time, concurrency — never with a retry, a sleep or a longer timeout.",
+    "A test that fails every run is a bug for the bugfix template; one that never fails is not fixed."
+  ],
+  "nodes": ["flake-repro", "identify", "apply", "flake-check", "test", "review"],
+  "start": "flake-repro",
+  "edges": [
+    { "from": "flake-repro", "on": "flaky", "to": "identify" },
+    { "from": "flake-repro", "on": "stable", "to": "$stop" },
+    { "from": "flake-repro", "on": "broken", "to": "$stop" },
+    { "from": "identify", "on": "more", "to": "apply" },
+    { "from": "identify", "on": "done", "to": "$close" },
+    { "from": "apply", "on": "pass", "to": "flake-check" },
+    { "from": "flake-check", "on": "stable", "to": "test" },
+    { "from": "flake-check", "on": "flaky", "to": "apply" },
+    { "from": "test", "on": "pass", "to": "review" },
+    { "from": "test", "on": "fail", "to": "apply" },
+    { "from": "review", "on": "pass", "to": "identify" },
+    { "from": "review", "on": "fail", "to": "apply" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "apply", "flake-check", "test", "review"], "max": 10, "iteration": true },
+    { "name": "stabilise", "nodes": ["apply", "flake-check"], "max": 4 },
+    { "name": "review-fix", "nodes": ["apply", "flake-check", "test", "review"], "max": 3 }
+  ]
+}

package/src/loops/legacy-refactor.json

@@ -0,0 +1,26 @@
+{
+  "name": "legacy-refactor",
+  "description": "Confirm the suite is green, pin the code's current behaviour with characterization tests in their own commit, then refactor behind that net: apply, test, and review, until the requirement is met.",
+  "category": "refactoring",
+  "nodes": ["baseline-green", "characterize", "identify", "apply", "test", "review"],
+  "start": "baseline-green",
+  "edges": [
+    { "from": "baseline-green", "on": "pass", "to": "characterize" },
+    { "from": "baseline-green", "on": "fail", "to": "$stop" },
+    { "from": "characterize", "on": "pass", "to": "identify" },
+    { "from": "characterize", "on": "fail", "to": "$stop" },
+    { "from": "identify", "on": "more", "to": "apply" },
+    { "from": "identify", "on": "done", "to": "$close" },
+    { "from": "apply", "on": "pass", "to": "test" },
+    { "from": "test", "on": "pass", "to": "review" },
+    { "from": "test", "on": "fail", "to": "apply" },
+    { "from": "review", "on": "pass", "to": "identify" },
+    { "from": "review", "on": "fail", "to": "apply" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "apply", "test", "review"], "max": 20, "iteration": true },
+    { "name": "apply-test", "nodes": ["apply", "test"], "max": 5 },
+    { "name": "review-fix", "nodes": ["apply", "test", "review"], "max": 3 }
+  ],
+  "weights": { "logic": 0.6 }
+}

package/src/loops/legacy-tests.json

@@ -0,0 +1,29 @@
+{
+  "name": "legacy-tests",
+  "description": "Confirm the suite is green, then pin legacy behaviour one change point at a time: characterization tests, a run, and a mutation check that proves they bite.",
+  "category": "tests",
+  "rules": [
+    "Tests only: production code is never touched."
+  ],
+  "nodes": ["baseline-green", "identify", "characterize", "test", "mutation-check"],
+  "start": "baseline-green",
+  "edges": [
+    { "from": "baseline-green", "on": "pass", "to": "identify" },
+    { "from": "baseline-green", "on": "fail", "to": "$stop" },
+    { "from": "identify", "on": "more", "to": "characterize" },
+    { "from": "identify", "on": "done", "to": "$close" },
+    { "from": "characterize", "on": "pass", "to": "test" },
+    { "from": "characterize", "on": "fail", "to": "$stop" },
+    { "from": "test", "on": "pass", "to": "mutation-check" },
+    { "from": "test", "on": "fail", "to": "characterize" },
+    { "from": "mutation-check", "on": "pass", "to": "identify" },
+    { "from": "mutation-check", "on": "fail", "to": "characterize" },
+    { "from": "mutation-check", "on": "unavailable", "to": "identify" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "characterize", "test", "mutation-check"], "max": 20, "iteration": true },
+    { "name": "write-run", "nodes": ["characterize", "test"], "max": 3 },
+    { "name": "kill-mutants", "nodes": ["characterize", "test", "mutation-check"], "max": 3 }
+  ],
+  "weights": { "new-file": 0.2 }
+}

package/src/loops/refactor.json

@@ -0,0 +1,24 @@
+{
+  "name": "refactor",
+  "description": "Confirm the suite is green before touching anything, then iterate on the shape of the code alone.",
+  "category": "refactoring",
+  "rules": [
+    "Tests are not edited: a refactor that needs a different test is a behaviour change, not a refactor."
+  ],
+  "nodes": ["baseline-green", "identify", "apply", "test"],
+  "start": "baseline-green",
+  "edges": [
+    { "from": "baseline-green", "on": "pass", "to": "identify" },
+    { "from": "baseline-green", "on": "fail", "to": "$stop" },
+    { "from": "identify", "on": "more", "to": "apply" },
+    { "from": "identify", "on": "done", "to": "$close" },
+    { "from": "apply", "on": "pass", "to": "test" },
+    { "from": "test", "on": "pass", "to": "identify" },
+    { "from": "test", "on": "fail", "to": "apply" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "apply", "test"], "max": 20, "iteration": true },
+    { "name": "apply-test", "nodes": ["apply", "test"], "max": 5 }
+  ],
+  "weights": { "logic": 0.6 }
+}

package/src/loops/remove-dead-code.json

@@ -0,0 +1,30 @@
+{
+  "name": "remove-dead-code",
+  "description": "Confirm the suite is green, then remove one coherent group of unused code per iteration — exports, classes, files, retired flags — test it, and review it. Deletions score soft, not blocking.",
+  "category": "refactoring",
+  "rules": [
+    "Each card's intent cites the proof it is unused: the requirement's tool output (knip, ts-prune, vulture, PMD or IntelliJ inspections) and a reference search (git grep over code AND resources) for reflection, DI by name, Spring bean names and config.",
+    "Generated sources do not count as unused.",
+    "Public entry points belong in LOOP.md's contracts, not in a deletion."
+  ],
+  "nodes": ["baseline-green", "identify", "apply", "test", "review"],
+  "start": "baseline-green",
+  "edges": [
+    { "from": "baseline-green", "on": "pass", "to": "identify" },
+    { "from": "baseline-green", "on": "fail", "to": "$stop" },
+    { "from": "identify", "on": "more", "to": "apply" },
+    { "from": "identify", "on": "done", "to": "$close" },
+    { "from": "apply", "on": "pass", "to": "test" },
+    { "from": "test", "on": "pass", "to": "review" },
+    { "from": "test", "on": "fail", "to": "apply" },
+    { "from": "review", "on": "pass", "to": "identify" },
+    { "from": "review", "on": "fail", "to": "apply" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "apply", "test", "review"], "max": 20, "iteration": true },
+    { "name": "apply-test", "nodes": ["apply", "test"], "max": 5 },
+    { "name": "review-fix", "nodes": ["apply", "test", "review"], "max": 3 }
+  ],
+  "weights": { "delete": 0.5 },
+  "ignoreDeletions": ["**/generated/**", "**/generated-sources/**", "**/target/**", "**/build/generated/**"]
+}

package/src/loops/spec-first-feature.json

@@ -0,0 +1,29 @@
+{
+  "name": "spec-first-feature",
+  "description": "Write the feature's spec first — specs/<slug>/spec.md with EARS acceptance criteria and an ordered task list — for the user to review, commit it, then build it task by task: apply, test, review. An independent done-check maps every criterion to a passing test before the loop closes.",
+  "category": "development",
+  "rules": [
+    "One spec task per iteration, in the spec's order.",
+    "Open questions in the spec wait for the user's answers; never answer them yourself."
+  ],
+  "nodes": ["spec", "identify", "apply", "test", "review", "done-check"],
+  "start": "spec",
+  "edges": [
+    { "from": "spec", "on": "pass", "to": "identify" },
+    { "from": "spec", "on": "fail", "to": "$stop" },
+    { "from": "identify", "on": "more", "to": "apply" },
+    { "from": "identify", "on": "done", "to": "done-check" },
+    { "from": "apply", "on": "pass", "to": "test" },
+    { "from": "test", "on": "pass", "to": "review" },
+    { "from": "test", "on": "fail", "to": "apply" },
+    { "from": "review", "on": "pass", "to": "identify" },
+    { "from": "review", "on": "fail", "to": "apply" },
+    { "from": "done-check", "on": "pass", "to": "$close" },
+    { "from": "done-check", "on": "fail", "to": "identify" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "apply", "test", "review", "done-check"], "max": 20, "iteration": true },
+    { "name": "apply-test", "nodes": ["apply", "test"], "max": 5 },
+    { "name": "review-fix", "nodes": ["apply", "test", "review"], "max": 3 }
+  ]
+}

package/src/loops/tdd.json

@@ -0,0 +1,25 @@
+{
+  "name": "tdd",
+  "description": "Plan the work, then build it test-first: each iteration writes a failing test, makes it pass, and reviews the diff, until the plan is complete.",
+  "category": "tests",
+  "nodes": ["plan", "identify", "red-test", "apply", "test", "review"],
+  "start": "plan",
+  "edges": [
+    { "from": "plan", "on": "pass", "to": "identify" },
+    { "from": "identify", "on": "more", "to": "red-test" },
+    { "from": "identify", "on": "done", "to": "$close" },
+    { "from": "red-test", "on": "red", "to": "apply" },
+    { "from": "red-test", "on": "green", "to": "test" },
+    { "from": "red-test", "on": "untestable", "to": "$stop" },
+    { "from": "apply", "on": "pass", "to": "test" },
+    { "from": "test", "on": "pass", "to": "review" },
+    { "from": "test", "on": "fail", "to": "apply" },
+    { "from": "review", "on": "pass", "to": "identify" },
+    { "from": "review", "on": "fail", "to": "apply" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "red-test", "apply", "test", "review"], "max": 20, "iteration": true },
+    { "name": "apply-test", "nodes": ["apply", "test"], "max": 5 },
+    { "name": "review-fix", "nodes": ["apply", "test", "review"], "max": 3 }
+  ]
+}

package/src/loops/update-contract.json

@@ -0,0 +1,33 @@
+{
+  "name": "update-contract",
+  "description": "Change an interface with live consumers — an API, a schema, an event — as expand, migrate one consumer per iteration, contract: plan it for the user to review, then apply, test, check old and new consumers, and review.",
+  "category": "architecture",
+  "rules": [
+    "Contract files (OpenAPI, AsyncAPI, protobuf, Avro, GraphQL schemas, Flyway and Liquibase migrations) stop for a human by default; a stop on one is expected, not a failure.",
+    "`geneseed loop init --contracts <globs>` appends more contract globs, and LOOP.md's `contracts` can be trimmed."
+  ],
+  "nodes": ["migration-plan", "identify", "apply", "test", "compat-check", "review"],
+  "start": "migration-plan",
+  "edges": [
+    { "from": "migration-plan", "on": "pass", "to": "identify" },
+    { "from": "migration-plan", "on": "fail", "to": "$stop" },
+    { "from": "identify", "on": "more", "to": "apply" },
+    { "from": "identify", "on": "done", "to": "$close" },
+    { "from": "apply", "on": "pass", "to": "test" },
+    { "from": "test", "on": "pass", "to": "compat-check" },
+    { "from": "test", "on": "fail", "to": "apply" },
+    { "from": "compat-check", "on": "pass", "to": "review" },
+    { "from": "compat-check", "on": "fail", "to": "apply" },
+    { "from": "review", "on": "pass", "to": "identify" },
+    { "from": "review", "on": "fail", "to": "apply" }
+  ],
+  "loops": [
+    { "name": "iterations", "nodes": ["identify", "apply", "test", "compat-check", "review"], "max": 20, "iteration": true },
+    { "name": "apply-test", "nodes": ["apply", "test"], "max": 5 },
+    { "name": "review-fix", "nodes": ["apply", "test", "compat-check", "review"], "max": 3 }
+  ],
+  "contracts": [
+    "**/openapi*.yaml", "**/openapi*.yml", "**/openapi*.json", "**/asyncapi*.yaml", "**/*.proto", "**/*.avsc",
+    "**/*.graphqls", "**/*.graphql", "**/asyncapi*.yml", "**/asyncapi*.json", "**/db/migration/**", "**/db/changelog/**"
+  ]
+}

package/src/skills/brick-forge.md

@@ -0,0 +1,48 @@
+# {{SKILL}}: brick-forge
+
+> {{DESC_BRICK_FORGE}}
+
+**Trigger:** the user wants a new loop brick, or to adapt an existing one to their stack — "make
+a brick for…", "our tests run differently, change the `test` brick", "the loop needs a step
+that…".
+
+## Procedure
+
+1. **Interview, one question at a time:**
+   - **name** — kebab-case, the file stem.
+   - **what it does** — one line; it becomes `description`.
+   - **effect** — does it ever create, edit or delete a file? Yes → `mutate`; never → `read`;
+     unsure → `mutate`. A `read` brick that writes stops the loop.
+   - **who runs it** — exactly one of an `agent` (one of the {{AGENTS}}) or a `skill`.
+   - **outcomes** — every result it can report, comma-separated. Each becomes an edge label a
+     loop graph must route (`{from, on: "<outcome>", to}`).
+   - **level** — project `<repo>/.geneseed/bricks/` (committed, shared with the team), global
+     `$XDG_CONFIG_HOME/geneseed/bricks/` (default `~/.config/geneseed/bricks/`, every project on
+     this machine), or shipped `src/bricks/` — only inside the Geneseed repository itself.
+2. **Write `<level>/<name>.md`**, the file stem equal to `name`:
+
+   ```
+   ---
+   name: <kebab-name>
+   description: <one line>
+   effect: read | mutate
+   agent: <agent>            (or  skill: <skill> — exactly one of the two)
+   outcomes: <a>, <b>
+   ---
+   <4-10 lines of direct instructions, ending with exactly how to choose among the outcomes>
+   ```
+
+   No double-brace tokens in the body: the loop hands it to the model raw. If the brick finds
+   something the next brick needs, have it write that to a file in the OS temp directory and
+   report the path with the outcome — the loop skill records it as a note.
+3. **Overriding by name** — a project or global brick named like a shipped one replaces it in
+   every template. That is allowed; say so to the user. `geneseed loop check` lists overrides under `overridden`.
+4. **Check it:** `geneseed loop check --brick <path>` (this file alone), then
+   `geneseed loop check` from the repository (the whole catalogue, including every template that
+   now routes through it). Fix every listed problem and re-run both.
+
+## Done when
+
+- The brick file exists at the chosen level, and both checks print `ok: true`.
+
+<!-- INCLUDE: skills/_self-improvement.md -->

package/src/skills/bruno-collection-generator.md

@@ -3,9 +3,9 @@
 > {{DESC_BRUNO_COLLECTION_GENERATOR}}
 
 **Trigger:** creating, converting, or reorganising a [Bruno](https://www.usebruno.com/)
-collection — requests, folders, environments, request docs — from backend routes, an
-OpenAPI snippet, pasted API docs, curl commands, or a plain endpoint list, as `.bru`
-files or OpenCollection YAML.
+collection as `.bru` files or OpenCollection YAML. The collection covers requests,
+folders, environments and request docs; the source can be backend routes, an OpenAPI
+snippet, pasted API docs, curl commands, or a plain endpoint list.
 
 ## Procedure
 1. Gather the inputs, and state every assumption you fill in ({{LAW:echo-the-intent}}): the source

package/src/skills/bruno-test-writer.md

@@ -3,9 +3,9 @@
 > {{DESC_BRUNO_TEST_WRITER}}
 
 **Trigger:** writing, reviewing, or strengthening tests for a [Bruno](https://www.usebruno.com/)
-request or collection — assertions, `tests` blocks, pre-request and post-response
-scripts, request chaining, schema checks, edge cases — in `.bru` files or
-OpenCollection YAML.
+request or collection in `.bru` files or OpenCollection YAML. Covers assertions, `tests`
+blocks, pre-request and post-response scripts, request chaining, schema checks, and
+edge cases.
 
 ## Procedure
 1. Understand the request or collection first: method, path, auth, body, headers,

package/src/skills/ci-fix.md

@@ -2,9 +2,9 @@
 
 > {{DESC_CI_FIX}}
 
-**Trigger:** a CI run, pipeline job, or pre-merge check is red — on a PR you opened, a
-branch you are on, or one the user points you at — or the user says "CI is failing",
-"fix the build", "why is the pipeline red". The [debug {{SKILL}}](debug.md) drives
+**Trigger:** a CI run, pipeline job, or pre-merge check is red, or the user says "CI is
+failing", "fix the build", "why is the pipeline red". The red run can be on a PR the agent
+opened, the branch it is on, or one the user points at. The [debug {{SKILL}}](debug.md) drives
 the root-causing once the failure reproduces locally; this {{SKILL}} gets it there and
 gets the fix back through the same gate.
 

package/src/skills/consolidate-memory.md

@@ -2,10 +2,10 @@
 
 > {{DESC_CONSOLIDATE_MEMORY}}
 
-**Trigger:** the {{MEMORY}} index has grown past what a session can usefully read
-(~40 lines), two entries say the same or opposite things, a memory names a file, flag,
-or command that no longer exists, a `feedback` lesson keeps recurring, or the user
-says "clean up memory", "consolidate", "what do you actually remember". Also worth a
+**Trigger:** the {{MEMORY}} index has outgrown one useful read (~40 lines) or holds
+duplicate, contradictory, or stale entries. Stale means a memory naming a file, flag, or
+command that no longer exists; a `feedback` lesson that keeps recurring counts too, as
+does the user saying "clean up memory", "consolidate", "what do you actually remember". Also worth a
 pass after a release or a large refactor, when many recorded facts just changed. The
 [rule {{SKILL}}](rule.md) writes one memory or one rule; this {{SKILL}} tends the
 whole set. The user's wiki is out of scope — that is the [wiki {{SKILL}}](wiki.md).

package/src/skills/council.md

@@ -2,7 +2,7 @@
 
 > {{DESC_COUNCIL}}
 
-**Trigger:** the user asks to "convene a council", "debate this", "argue both sides", "stress-test this decision", or wants a change, plan, or claim challenged from several points of view before committing to it.
+**Trigger:** the user asks to "convene a council", "debate this", or "argue both sides", or wants a decision stress-tested from several points of view. A change, plan, or claim all qualify, as long as it is challenged before committing to it.
 
 ## Procedure
 1. Frame the motion in one line — the exact decision, change, or claim under debate — and name what it feeds (a choice to make, a design to accept, a discussion to settle). Ground it in the real artifact and the project's own docs ({{DOCTRINE:read-the-docs-first}}) so the council argues the actual thing; if the motion is unclear or bundles several questions, split it and ask once, then proceed.

package/src/skills/fresh-eyes.md

@@ -2,7 +2,7 @@
 
 > {{DESC_FRESH_EYES}}
 
-**Trigger:** a task is claimed done and the solving session believes the artifact works — before merge or handoff, or when the user asks to "validate", "fresh eyes", "prove it meets the spec", "did this actually solve it", or "independent sign-off", and the cost of a confidently-wrong "done" is high. This re-judges the *result* from zero context — distinct from [geneseed-code-review](geneseed-code-review.md), which reviews a *diff* with full knowledge of the change. For an open-ended quality critique use [roast-me](roast-me.md); for a multi-stance debate over an undecided question use [council](council.md).
+**Trigger:** work is claimed done and needs a blind check against the original ask. That is before merge or handoff, while the solving session believes the artifact works, or when the user asks to "validate", "fresh eyes", "prove it meets the spec", "did this actually solve it", or "independent sign-off" — and the cost of a confidently-wrong "done" is high. This re-judges the *result* from zero context — distinct from [geneseed-code-review](geneseed-code-review.md), which reviews a *diff* with full knowledge of the change. For an open-ended quality critique use [roast-me](roast-me.md); for a multi-stance debate over an undecided question use [council](council.md).
 
 ## Procedure
 1. Capture the firewall input as TWO things and nothing else: (a) the **verbatim original task/spec** — the raw issue or request text, NOT a solver-written summary or "spec card" (a distilled card launders the solving session's framing into the rubric, the very bias this {{SKILL}} exists to defeat), and (b) a pointer to the **final artifact** as it stands — file paths, built output, or the command to run it. If the raw task is too thin to yield acceptance criteria, have the **user** (never the solver) confirm a one-line acceptance bar, then proceed ({{LAW:echo-the-intent}}); if it is too fuzzy even for that, this is a judgement call — convene [council](council.md) instead.

package/src/skills/geneseed.md

@@ -8,7 +8,7 @@
 1. **Locate.** Run `geneseed status --json` first: `installs` lists every install on this machine — host, scope, root, state, theme, footprint, posture, mode, packs, excluded rules — and `rebuild`, the command that reproduces each one exactly. `geneseed` not on PATH → ask the user before using `npx geneseed` (it downloads the package), and prefix every command below the same way. Still nothing → look for a host root file: `~/.config/opencode/AGENT.md` or `.opencode/AGENT.md` (OpenCode), `~/.claude/CLAUDE.md` or `.claude/` (Claude Code), `.openclaude/` (OpenClaude), `AGENTS.md` beside `.bob/` (Bob). None → say so; never install to "fix" it.
 2. **Read state** with the read-only verbs, cheapest first ({{DOCTRINE:context-economy}}): `geneseed status --json`, `geneseed version`, `geneseed catalog` (optionally `agents|skills|laws|ontology|doctrines`), `geneseed doctor`, `geneseed diff`, `geneseed mcp`, `geneseed memory list`, `geneseed exclude list`.
 3. **Read a piece** from disk, not from recall ({{LAW:verify-before-asserting}}): `<root>/agents/<name>.md`, `<root>/skills/<name>/SKILL.md`, `<root>/memory/`, `<root>/notebook/`. The {{ONTOLOGY}}, the {{LAWS}} and the active {{DOCTRINES}} are numbered `## N. …` sections of the install's root file.
-4. **Change an install only when the user asked for that change** ({{LAW:one-intent-one-act}}). Take that install's `rebuild` command from step 1, edit only the flag the user named (add it if the command omits it — `--posture` and `--mode` are left out at their defaults) — `--theme`, `--footprint lean|full`, `--posture`, `--mode direct|foreman`, `--doctrines craft,rigor|none`, `--exclude-rules "process 7"|none` — dry-run it first by running the same flags through `geneseed validate`, show the command, and run it once the user agrees. Never rebuild from a bare `geneseed build`: every omitted flag resets that setting to the generator default. Confirm with `geneseed status`.
+4. **Change an install only when the user asked for that change** ({{LAW:one-intent-one-act}}). Take that install's `rebuild` command from step 1, edit only the flag the user named (add it if the command omits it — `--posture`, `--mode` and `--trust` are left out at their defaults) — `--theme`, `--footprint lean|full`, `--posture`, `--mode direct|foreman`, `--trust prudent|balanced|aggressive`, `--doctrines craft,rigor|none`, `--exclude-rules "process 7"|none` — dry-run it first by running the same flags through `geneseed validate`, show the command, and run it once the user agrees. Never rebuild from a bare `geneseed build`: every omitted flag resets that setting to the generator default. Confirm with `geneseed status`.
 5. **Other writes also need the user's word:** `geneseed memory rm <name>`, `geneseed exclude add|remove <path>`, `geneseed web start|stop`, `geneseed uninstall --target <root> --yes`. Personal rules and the profile belong to their own {{SKILLS}}; do not edit `user-rules.md` or `PROFILE.md` from here.
 6. **Never on your own initiative:** `geneseed setup` (interactive only), `geneseed upgrade`, `geneseed update`, `geneseed bootstrap`, `geneseed sync-self`, `geneseed rebuild-all`, `geneseed migrate`, `geneseed link`, `geneseed unlink`. `learn`, `context` and the `*-gate` verbs are `geneseed-hook` verbs the host's hooks run — never run them by hand.
 7. Directory and section names are plain English in every theme; only prose changes. Do not search by flavour words.

package/src/skills/git-archaeology.md

@@ -2,7 +2,7 @@
 
 > {{DESC_GIT_ARCHAEOLOGY}}
 
-**Trigger:** you need to learn something *from* the history — when a regression was
+**Trigger:** something must be learned *from* the history — when a regression was
 introduced, who last touched a line and why, or where a symbol or string entered the
 codebase. Read-only: this {{SKILL}} investigates, it does not change history (to repair
 or rewrite, use git-rescue.md; to write a new commit, use commit.md).

package/src/skills/git-rescue.md

@@ -2,9 +2,10 @@
 
 > {{DESC_GIT_RESCUE}}
 
-**Trigger:** the repository is in a broken or messy state — a bad rebase/merge/reset,
-lost commits, a detached HEAD, a half-finished operation, work stranded in a stash — or
-you intend to deliberately rewrite history (interactive rebase, squash, amend). For
+**Trigger:** commits are lost, a rebase/merge/reset went wrong, or history is to be
+deliberately rewritten (interactive rebase, squash, amend). The repository can also be
+messy in other ways: a detached HEAD, a half-finished operation, or work stranded in a
+stash. For
 finding *when/why* something changed without altering history, use git-archaeology.md.
 
 ## Procedure

package/src/skills/handoff.md

@@ -2,7 +2,7 @@
 
 > {{DESC_HANDOFF}}
 
-**Trigger:** the context window is filling, a session is ending mid-task, or you're passing work to another agent or developer.
+**Trigger:** the context window is filling, a session is ending mid-task, or work is passing to another agent or developer.
 
 ## Procedure
 1. Capture the state in the worklog (`WORKLOG.md` or the task's plan file): the goal, what's done, the step in progress, and the exact next step.

package/src/skills/herdr.md

@@ -4,7 +4,7 @@
 > {{DESC_HERDR}}
 <!-- invocation: user -->
 
-**Trigger:** you are running inside a herdr-managed pane (`HERDR_ENV=1`) and a task would benefit from another pane — splitting off a server, watching a long-running build, spawning a sibling agent, or reading what a neighbour is doing. If `HERDR_ENV` is unset or not `1`, you are not inside herdr — stop and do not try to control panes from outside.
+**Trigger:** the session runs inside a herdr-managed pane (`HERDR_ENV=1`) and a task would benefit from another pane. Typical cases: splitting off a server, watching a long-running build, spawning a sibling agent, or reading what a neighbour is doing. If `HERDR_ENV` is unset or not `1`, you are not inside herdr — stop and do not try to control panes from outside.
 
 **Requires:** `HERDR_ENV=1` in the environment and the `herdr` binary on `PATH`.
 

package/src/skills/learn-mode.md

@@ -4,8 +4,8 @@
 
 <!-- invocation: user -->
 
-**Trigger:** the user wants to *learn while building* rather than be handed finished code —
-"learn mode", "turn on learning", "I want to understand what we build", "let me design it,
+**Trigger:** the user wants to *learn while building* rather than be handed finished code.
+Phrases: "learn mode", "turn on learning", "I want to understand what we build", "let me design it,
 you write it". Also "pause learning" / "resume learning" / "stop learn mode". To be taught a
 topic outside a build, use the [teach {{SKILL}}](teach.md); to have knowledge tested, the
 [quiz {{SKILL}}](quiz.md).