@mrciphersmith/keryx 0.2.76 → 0.2.77

package/src/gdskills/bundled/skills/orchestration/task-implementer/SKILL.opencode.md

@@ -534,10 +534,8 @@ second copy of a schema is how that happens.
 9. **DO** verify your work before reporting.
 10. **DO** make `STATUS: <TOKEN>` the first line of your final message, and put no
     JSON in the response body. The full JSON result is the file Phase 6.1 writes
-    and records. (This rule used to say the opposite — "return the JSON result
-    object as your final message" — which contradicted 6.2, `## Reporting
-    Results`, and `parseChildResult`, the production function that throws on any
-    first line that is not a canonical STATUS token.)
+    and records. `parseChildResult` throws on any first line that is not a
+    canonical STATUS token.
 
 ---
 

package/src/gdskills/bundled/skills/orchestration/task-implementer/SKILL.zed.md

@@ -534,10 +534,8 @@ second copy of a schema is how that happens.
 9. **DO** verify your work before reporting.
 10. **DO** make `STATUS: <TOKEN>` the first line of your final message, and put no
     JSON in the response body. The full JSON result is the file Phase 6.1 writes
-    and records. (This rule used to say the opposite — "return the JSON result
-    object as your final message" — which contradicted 6.2, `## Reporting
-    Results`, and `parseChildResult`, the production function that throws on any
-    first line that is not a canonical STATUS token.)
+    and records. `parseChildResult` throws on any first line that is not a
+    canonical STATUS token.
 
 ---
 

package/src/gdskills/bundled/skills/planning/autodoc-orchestrator/SKILL.md

@@ -3,13 +3,17 @@ name: autodoc-orchestrator
 description: >
   Autonomous reverse-engineering documentation pipeline — scans an existing codebase
   and produces comprehensive developer documentation without user involvement after initial setup.
-  Use when: "autodoc", "generate docs for my project", "document this codebase",
-  "reverse engineer documentation", "create project documentation from code",
-  "сгенерируй документацию проекта", "задокументируй кодовую базу",
-  "автодок", "autodoc".
-  Trigger on: user provides a repo path, asks to document existing code, wants
-  onboarding docs, API reference, or architecture overview generated automatically.
+  Use when the user provides a repo path, asks to document existing code, or wants
+  onboarding docs, an API reference, or an architecture overview generated automatically.
   NOT for: writing new PRDs or planning new features (use gproject-orchestrator).
+triggers:
+  - "autodoc"
+  - "автодок"
+  - "document this codebase"
+  - "generate docs for my project"
+  - "reverse engineer documentation"
+  - "задокументируй кодовую базу"
+  - "сгенерируй документацию проекта"
 metadata:
   version: 1.0.0
 ---

package/src/gdskills/bundled/skills/planning/interview/SKILL.codex.md

@@ -1,6 +1,6 @@
 ---
 name: interview
-description: "Use before implementation, design, or migration when requirements are unclear and targeted clarifying questions are needed to gather precise context."
+description: "Use to clarify implementation-specific ambiguities AFTER context has already been collected and the goal is known — the questions that sharpen a plan, not the ones that scope the request. This is the `implement`-intent interview job-orchestrator runs at 0.3. To pin down a vague request before any context is gathered, use `interviewer` instead."
 triggers:
   - "/interview"
   - "Interview"

package/src/gdskills/bundled/skills/planning/interview/SKILL.cursor.md

@@ -1,6 +1,6 @@
 ---
 name: interview
-description: "Use before implementation, design, or migration when requirements are unclear and targeted clarifying questions are needed to gather precise context."
+description: "Use to clarify implementation-specific ambiguities AFTER context has already been collected and the goal is known — the questions that sharpen a plan, not the ones that scope the request. This is the `implement`-intent interview job-orchestrator runs at 0.3. To pin down a vague request before any context is gathered, use `interviewer` instead."
 triggers:
   - "/interview"
   - "Interview"

package/src/gdskills/bundled/skills/planning/interview/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: interview
-description: "Use before implementation, design, or migration when requirements are unclear and targeted clarifying questions are needed to gather precise context."
+description: "Use to clarify implementation-specific ambiguities AFTER context has already been collected and the goal is known — the questions that sharpen a plan, not the ones that scope the request. This is the `implement`-intent interview job-orchestrator runs at 0.3. To pin down a vague request before any context is gathered, use `interviewer` instead."
 triggers:
   - "/interview"
   - "Interview"

package/src/gdskills/bundled/skills/planning/interviewer/SKILL.codex.md

@@ -1,6 +1,6 @@
 ---
 name: interviewer
-description: "Use when requirements are ambiguous and precise clarification is needed before proceeding with a complex task."
+description: "Use when a request is ambiguous and must be pinned down BEFORE any context is collected — the entry-point interview that turns a vague or expensive ask into a scoped brief. This is the `custom`-intent gate job-orchestrator runs at 0.1.5. For clarifying implementation specifics AFTER context is already collected, use `interview` instead."
 triggers:
   - "Interview me"
   - "Ask me questions"

package/src/gdskills/bundled/skills/planning/interviewer/SKILL.cursor.md

@@ -1,6 +1,6 @@
 ---
 name: interviewer
-description: "Use when requirements are ambiguous and precise clarification is needed before proceeding with a complex task."
+description: "Use when a request is ambiguous and must be pinned down BEFORE any context is collected — the entry-point interview that turns a vague or expensive ask into a scoped brief. This is the `custom`-intent gate job-orchestrator runs at 0.1.5. For clarifying implementation specifics AFTER context is already collected, use `interview` instead."
 triggers:
   - "Interview me"
   - "Ask me questions"

package/src/gdskills/bundled/skills/planning/interviewer/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: interviewer
-description: "Use when requirements are ambiguous and precise clarification is needed before proceeding with a complex task."
+description: "Use when a request is ambiguous and must be pinned down BEFORE any context is collected — the entry-point interview that turns a vague or expensive ask into a scoped brief. This is the `custom`-intent gate job-orchestrator runs at 0.1.5. For clarifying implementation specifics AFTER context is already collected, use `interview` instead."
 triggers:
   - "Interview me"
   - "Ask me questions"

package/src/gdskills/bundled/skills/platform/agent-entrypoint-distiller/SKILL.md

@@ -1,6 +1,10 @@
 ---
 name: agent-entrypoint-distiller
 description: Use when the user asks to split, decompose, distill, or refactor a large AGENTS.md or CLAUDE.md into Metaproject rules and project-specific skills while keeping root entrypoints compact.
+triggers:
+  - "distill AGENTS.md"
+  - "split CLAUDE.md"
+  - "разнеси CLAUDE.md по правилам"
 metadata:
   version: "1.0.0"
   category: platform

package/src/gdskills/bundled/skills/review/review-architecture/SKILL.md

@@ -5,8 +5,7 @@ description: |
   Use when: reviewing code for architectural violations — layer violations, dependency direction
   mistakes, module boundary coupling, SOLID principle breaches, NestJS module/provider structure,
   React MVVM boundary violations, or MobX store layer misplacement.
-  Triggered by: "review architecture", "check architecture", "architectural review",
-  or dispatched by review-orchestrator with --architecture or --backend.
+  Dispatched by review-orchestrator with --architecture or --backend.
   NOT for: style/naming preferences, logic correctness bugs, or security vulnerabilities.
 triggers:
   - "review architecture"

package/src/gdskills/bundled/skills/review/review-backend/SKILL.md

@@ -3,8 +3,8 @@ name: review-backend
 model_tier: standard
 description: |
   Use when: reviewing NestJS backend changes — API design, service layer, DTO validation,
-  database patterns, and TypeScript correctness. Covers "review backend", "backend review",
-  "review API", "review NestJS", or dispatched by review-orchestrator with --backend flag.
+  database patterns, and TypeScript correctness. Dispatched by review-orchestrator
+  with the --backend flag.
   NOT for: frontend patterns, MobX, React components, general security vulnerabilities
   (use review-security-code for XSS/injection/auth-bypass), or performance profiling
   (use review-performance).

package/src/gdskills/bundled/skills/review/review-clean-code/SKILL.md

@@ -6,8 +6,7 @@ description: |
   function/class level — meaningful names, small functions, single level of abstraction,
   argument count, error handling, DRY, comment quality, and SOLID (SRP, OCP, LSP, ISP, DIP)
   as applied to individual classes and functions.
-  Triggered by: "review clean code", "check clean code", "Uncle Bob review", "SOLID review",
-  "review --clean-code", or dispatched by review-orchestrator.
+  Dispatched by review-orchestrator.
   NOT for: architectural layer violations (review-architecture), naming convention formatting
   (review-style), logic correctness bugs (review-logic), or security (review-security-code).
 triggers:

package/src/gdskills/bundled/skills/review/review-core-boundaries/SKILL.md

@@ -6,6 +6,10 @@ description: |
   direction, feature-boundary leakage, abstraction stability, composition,
   and blast-radius risks. Dispatched by review-orchestrator for
   --core-boundaries, --project-conventions, --all, or src/core/** changes.
+triggers:
+  - "review core boundaries"
+  - "review --core-boundaries"
+  - dispatched by review-orchestrator
 metadata:
   author: "MrCipherSmith"
   version: "1.0.0"

package/src/gdskills/bundled/skills/review/review-flow-graph/SKILL.md

@@ -7,6 +7,10 @@ description: |
   boundaries, selection lifecycle, and large-graph performance. Dispatched by
   review-orchestrator for --flow-graph, --project-conventions, --all, or
   src/core/flow/** / graph abstraction changes.
+triggers:
+  - "review flow graph"
+  - "review --flow-graph"
+  - dispatched by review-orchestrator
 metadata:
   author: "MrCipherSmith"
   version: "1.0.0"

package/src/gdskills/bundled/skills/review/review-frontend-conventions/SKILL.md

@@ -8,6 +8,10 @@ description: |
   styling tokens, Storybook expectations, and local tooling rules. Dispatched
   by review-orchestrator for --frontend-conventions, --project-conventions,
   --all, or frontend src/**/*.ts(x) changes when local convention docs exist.
+triggers:
+  - "review frontend conventions"
+  - "review --frontend-conventions"
+  - dispatched by review-orchestrator
 metadata:
   author: "MrCipherSmith"
   version: "1.0.0"

package/src/gdskills/bundled/skills/review/review-highload/SKILL.md

@@ -6,8 +6,7 @@ description: |
   race conditions, connection pool exhaustion, cache invalidation, missing indexes,
   unbounded queues, missing backpressure, retry storms, idempotency gaps,
   hot-path blocking I/O, and distributed systems anti-patterns.
-  Triggered by: "review highload", "review scalability", "highload review",
-  "review concurrency", "review --highload", or dispatched by review-orchestrator.
+  Dispatched by review-orchestrator.
   NOT for: frontend re-render performance (review-performance), general N+1 queries
   (review-performance), clean code style (review-clean-code), or NestJS module structure
   (review-architecture).

package/src/gdskills/bundled/skills/review/review-orchestrator/SKILL.md

@@ -204,9 +204,8 @@ keryx review complete <review-id-or-path>
                       [--finding <id> --disposition <state> --evidence <ref>]...
 ```
 
-**An unrecognised option is refused, not ignored.** A misspelling used to be
-accepted with exit 0, so `review complete --disposition ...` printed
-`status: closed` and wrote nothing at all.
+**An unrecognised option is refused, not ignored** — a misspelled flag exits
+non-zero rather than printing `status: closed` and writing nothing at all.
 
 `--verifications` takes what `review-verifier` returned. `--scope` takes the
 whole `--json` output of `keryx review scope`, so the package records what the
@@ -679,16 +678,12 @@ A **fix round** is any review of work produced to answer earlier findings. Set
 `is_fix_round: true` on every reviewer input, and populate `prior_findings` with
 the earlier findings and the disposition the fix claimed for each.
 
-**Nothing refuses a dispatch that omits them, and this file used to say
-otherwise.** `reviewer-input.schema.json` states the rule and no production
-TypeScript loads that schema; reviewer dispatch is an action the host agent
-takes, not a `keryx` invocation, so there is no point at which a malformed
-dispatch could be rejected. `reviewer-input` is also absent from the `CONTRACTS`
-registry (`src/gdskills/contracts.ts`), so `keryx skills contracts validate`
-cannot be pointed at it either. The sentence that stood here until flow 209 told
-you the schema would reject a dispatch without `prior_findings`; it asserted an
-enforcement that has never existed, which is the same class of claim this whole
-package was written to delete.
+**Nothing refuses a dispatch that omits them.** `reviewer-input.schema.json`
+states the rule and no production TypeScript loads that schema; reviewer
+dispatch is an action the host agent takes, not a `keryx` invocation, so there
+is no point at which a malformed dispatch could be rejected. `reviewer-input` is
+also absent from the `CONTRACTS` registry (`src/gdskills/contracts.ts`), so
+`keryx skills contracts validate` cannot be pointed at it either.
 
 So this is a requirement on you, unenforced, and the only evidence it was met is
 the `prior_findings` array the reviewer actually receives. A reviewer that cannot

package/src/gdskills/bundled/skills/review/review-pr-feedback/SKILL.md

@@ -4,9 +4,8 @@ model_tier: standard
 description: |
   Use when: a developer has received PR review comments and wants to understand them,
   check whether they are still true of the code, act on them, or extract patterns
-  from them. Covers "analyze PR comments", "review PR feedback", "what did reviewers
-  say", "parse PR #N", "explain PR comments", and — with `--fix` — validating every
-  comment, planning the fix, driving it to a merged state and answering each reviewer.
+  from them. With `--fix`, also validates every comment, plans the fix, drives it to
+  a merged state and answers each reviewer.
   NOT for: reviewing code directly — this skill reads human or bot PR feedback and
   makes it actionable. To review code, use the domain review skills.
 triggers:

package/src/gdskills/bundled/skills/review/review-style/SKILL.md

@@ -3,9 +3,8 @@ name: review-style
 model_tier: light
 description: |
   Use when: reviewing code for style, naming conventions, readability, and DRY violations —
-  without touching logic, architecture, security, or performance. Covers "review style",
-  "style review", "check naming", "check readability", or dispatched by review-orchestrator
-  with --style flag.
+  without touching logic, architecture, security, or performance. Dispatched by
+  review-orchestrator with the --style flag.
   NOT for: logic bugs, architectural violations, security vulnerabilities, performance
   anti-patterns, or any finding that could cause a functional regression.
 triggers:

package/src/gdskills/bundled/skills/review/review-testing-practices/SKILL.md

@@ -10,6 +10,11 @@ description: |
   cannot fail is found by executing it rather than by reading it.
   Dispatched by review-orchestrator for --testing-practices,
   --project-conventions, --all, or changed test/e2e/story files.
+triggers:
+  - "review tests"
+  - "review testing practices"
+  - "review --testing-practices"
+  - dispatched by review-orchestrator
 metadata:
   author: "MrCipherSmith"
   version: "1.1.0"

package/src/gdskills/bundled/skills/review/review-verifier/SKILL.md

@@ -4,8 +4,7 @@ model_tier: light
 description: |
   Use when: consolidated findings from other reviewers need to be checked before they are
   reported — by RUNNING something that fails if the finding is real, or by confirming the
-  sites the finding named actually exist. Covers "verify the findings", "check these
-  findings", "review --verify", or dispatched by review-orchestrator as Wave C.
+  sites the finding named actually exist. Dispatched by review-orchestrator as Wave C.
   This reviewer can only DELETE. It cannot raise a severity, add a finding, or change a
   finding's text.
   NOT for: first-pass review (run domain reviewers first); re-scoring findings by re-reading