enigma-cli 1.21.2 → 1.22.0

package/assets/commands/gate.md

@@ -0,0 +1,131 @@
+---
+description: Validate code changes through the enigma gate pipeline - automated review, tests, lint, docs, push, PR, and CI - before they reach the configured push target. Use when the user asks to run the gate, gate/ship/validate their changes, push safely, do a task and then validate it, or invokes /gate.
+argument-hint: [task] | (bare to gate already-committed work) | "skip the lint step"-style requests
+---
+
+# /gate
+
+The enigma gate is a local gate that validates code changes through a pipeline
+(intent, rebase, review, test, document, lint, push, PR, CI) before they reach
+the configured push target. You drive it through the `enigma gate axi` command
+family, which prints machine-readable [TOON](https://toonformat.dev) to stdout
+and progress to stderr.
+
+The invocation is: **$ARGUMENTS**
+
+When the user invokes `/gate`, report the outcome at the end. If the user asks
+for something specific, translate it into the matching `axi run` flags yourself -
+for example "skip the lint step" becomes `--skip=lint`. Run
+`enigma gate axi run --help` to see the flags.
+
+## Two ways to invoke
+
+- **Validate-only** - bare `/gate` (optionally with flag-style requests like
+  "skip the lint step"). The user's changes are already committed; validate them
+  and report.
+- **Task-first** - `/gate <task>`, e.g. `/gate add a --json flag to status`. First
+  carry out the task yourself, then validate:
+  1. **Check scope.** Inspect `git status` before changing or committing anything.
+     Preserve unrelated uncommitted changes; commit only what belongs to the task.
+  2. **Do the work**, then **commit it on a feature branch**. If the user is on
+     the default branch, create a feature branch first - the gate validates
+     committed history on a non-default branch.
+  3. **Then validate**, passing the user's task as your `--intent` (the goal in
+     their words), enriched with the decisions and tradeoffs you made.
+
+## Before you start
+
+- The work must be **committed** on a **feature branch** (not the default branch).
+- The repository must be initialized with `enigma gate init`.
+
+If any precondition fails, `axi run` returns an `error:` with the exact fix -
+read it and act on it. If the repo is not initialized, run `enigma gate init`
+first; if `enigma gate` itself misbehaves, `enigma gate doctor` reports what is
+wrong. Before starting, run `enigma gate axi` (home view): if it shows an active
+run on your branch, resume it or `axi abort` before starting over; on another
+branch, leave it alone and start your own with
+`enigma gate axi run --intent "..."`.
+
+## Intent is required
+
+When you start a run you must pass `--intent`: **what the user set out to
+accomplish** - the goal behind the work, in their terms, not a description of the
+diff. Err on the side of completeness: capture the goal, the decisions and
+tradeoffs, constraints ruled in or out, and anything explicitly asked for that
+might look surprising in the diff. A few sentences is normal - the review step
+uses `--intent` to tell a deliberate choice from a mistake.
+
+## Validate and decide
+
+1. Start the run. It blocks until the first decision point or the end:
+   ```sh
+   enigma gate axi run --intent "<what the user set out to accomplish>"
+   ```
+   `axi run` and every `axi respond` block synchronously - review, test, and CI
+   can each take several minutes, so a single call may not return for a while.
+   That is normal; allow a long timeout and do not cancel or re-issue it. To
+   check progress, use `enigma gate axi status` from a separate call. When status
+   shows `awaiting_agent: parked <duration>`, the run is parked at a gate waiting
+   for your `axi respond`.
+2. If the output contains a `gate:` object, the pipeline is waiting on you. Read
+   its `findings` table. Each finding has an `action`:
+   - `auto-fix` - mechanical, low-risk; authorize on your own judgment with
+     `--action fix`.
+   - `no-op` - informational; nothing to do.
+   - `ask-user` - a judgment call only the user can make. STOP and escalate it
+     (see below) before responding.
+
+   Choose one response:
+   ```sh
+   enigma gate axi respond --action approve
+   enigma gate axi respond --action fix --findings <id1,id2> --instructions "<optional>"
+   enigma gate axi respond --action skip
+   ```
+   While a run is active, never fix findings by editing code yourself - the
+   pipeline owns the findings and the fixes. Decide and respond; `--action fix`
+   has the pipeline apply the fix and re-review.
+3. Repeat step 2 until the output has an `outcome:` instead of a `gate:`:
+   - `checks-passed` - validated and CI green, PR not merged yet. You are done
+     driving. Tell the user the PR is ready and ask them to review and merge it
+     (link in the `help` line). The gate keeps monitoring the PR in the
+     background; do not poll for the merge.
+   - `passed` - cleared the gate and the PR was merged or closed.
+   - `failed` / `cancelled` - read the output, fix what it points at, commit on
+     the same branch, and drive again (`axi run` for a fresh run, or
+     `enigma gate rerun`). Do not leave the user at a failed outcome without
+     either retrying or explaining what blocks it.
+
+On a successful outcome, summarize what the pipeline validated and found. If the
+output includes a `fixes` table, the pipeline fixed things your change missed -
+acknowledge those and list each fix.
+
+## Escalate ask-user findings
+
+A finding marked `ask-user` is the user's decision, not yours. Relay it verbatim
+(its `id`, `file`, full `description`) - do not paraphrase or pre-judge - ask how
+to proceed, then translate their answer into the matching `respond` call. The one
+exception is `--yes` (below): standing consent to drive every gate unattended.
+
+If you have clear consent to drive the whole run automatically, pass `--yes` to
+`axi run` or `axi respond`: it treats every actionable finding (auto-fix and
+ask-user alike) as consent to fix, accepts the resulting fix review, and approves
+no-op-only gates. Only use it when the user asked you to drive without checking back.
+
+## Inspecting state
+
+```sh
+enigma gate axi               # home view
+enigma gate axi status        # full detail of the resolved run
+enigma gate axi logs --step <name> --full
+enigma gate axi abort         # cancel the current-branch active run
+enigma gate axi abort --run <id>   # cancel a specific run by id
+```
+
+## Reading the output
+
+- TOON: `key: value` pairs, `name[N]{cols}:` tables, `help[N]:` hints. The `help`
+  list tells you the next commands. Errors print as `error: ...` with a `help`
+  list - act on the suggestion.
+- Exit codes: `0` success/no-op/decision-gate, `1` failed/cancelled, `2` bad usage.
+- Field names and columns can vary by step and version, so read the actual
+  `findings` header rather than assuming a fixed layout.

package/assets/skills/anti-overengineering-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Minimal-code discipline - YAGNI ladder, deletion over addition, no unrequested abstractions, and the enigma: shortcut-marking convention; intensity via the minimal-code setting.",
   "updated": "2026-06-25T17:21:31+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "b9517e7d520e83a9f881fb1917ca2d4cec4aea4f2c5e753ea02641d9bc06c6b6"
 }

package/assets/skills/anti-overengineering-review/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "On-demand over-engineering review - diff review, whole-repo audit, and enigma: debt-marker ledger (tags delete/stdlib/native/yagni/shrink, line/dep scoring); lists cuts, applies nothing.",
   "updated": "2026-06-16T11:24:30+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "f742a2be3f328b9ea1ff9a35a449177c2cbec35ad16e46f7054b7a873a2ab017"
 }

package/assets/skills/backend-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Backend/API architecture: controller-service-repository layering, API and request optimization, server-side caching (Redis), and Zod boundary validation.",
   "updated": "2026-06-16T12:06:06+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "a46c3cd00aa5f47adb1e7907f1d2bc6f5562f7a272890dee9b1121976ac04ae1"
 }

package/assets/skills/ciphera-style-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Ciphera code style conventions (formatting, naming, imports, comments, code-level anti-patterns; TypeScript-first, language-agnostic).",
   "updated": "2026-06-26T13:40:52+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "dc9ceb784004b05a0117c464e4bed05946835a04acea282586c0b735ee7c2284"
 }

package/assets/skills/code-review-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Pre-delivery self-review gate, prioritized review dimensions, and change-quality criteria.",
   "updated": "2026-06-01T00:45:28+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "3d3bbe0602d5bbb4afe37648fe3c2fa39376b1bcbac5d8c441f01fad1e866ed0"
 }

package/assets/skills/core-engineering-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Core engineering execution policy and harness orchestration (highest-authority rules).",
   "updated": "2026-06-25T17:54:55+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "5e68e2a25c8e3dac6251562062f7fe4c57143baaaee8fd6de83adca9ec24a6e6"
 }

package/assets/skills/database-expert/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Senior database architecture policy: query optimization, anti-duplication/normalization, scalability, and RGPD/GDPR encryption.",
   "updated": "2026-06-03T14:19:50+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "2883bcecb3202683ae6f81b073c3d6a9cec9c55029e011bdd06ba7ac3537297e"
 }

package/assets/skills/debugging-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Reproduce-isolate-fix debugging methodology with root-cause discipline and regression verification.",
   "updated": "2026-06-01T00:45:28+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "14b0064c8b33a0dc85e51464b05005cf5801c756b1101789a6924b9548420f6b"
 }

package/assets/skills/dependency-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Dependency and supply-chain security: lockfiles and reproducible installs, version pinning, vulnerability auditing, vetting/minimizing packages, vendoring, and SBOM/provenance.",
   "updated": "2026-06-01T00:45:28+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "6375d835c2aef2c9bd31ce116444dc3d796f510f9970a213aa3ac4696d7e21b9"
 }

package/assets/skills/frontend-design/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one.",
   "updated": "2026-06-25T15:51:43-04:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "fb78be3233bf9caa67d1f522c19831542b23f47e440b02211b5a950c898318b9"
 }

package/assets/skills/frontend-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Frontend architecture: reusable components, abstraction thresholds, state management, no-op save detection, large-list rendering (infinite scroll/pagination, virtualization, skeletons, progressive loading), and optimistic UI with rollback.",
   "updated": "2026-06-26T13:57:02+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "41cb938c9022efcdadc3056417cc7d442511adee40b09a141f11bb5fd9d56514"
 }

package/assets/skills/git-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Git & contribution policy (senior engineering standards).",
   "updated": "2026-06-25T17:14:54+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "9298bf572c6186de65bfae5cc008af247731fac3e07d9320ddfc12fe886d6afe"
 }

package/assets/skills/security-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Application and AI-agent security: secrets, authn/authz (least privilege), OWASP Top 10, transport/crypto baseline, secure logging, and agent/MCP/tool-use safety.",
   "updated": "2026-06-01T00:45:28+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "9971e9d9127397d0152e89d24aad3191e2935e55a8483db7fd15f5d4d7a60e7a"
 }

package/assets/skills/skill-creator/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Create new skills, modify and improve existing skills, and measure skill performance with evals and benchmarks.",
   "updated": "2026-06-16T16:39:13+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "699586cce82ec0a5458288b598ee7e5ebdddb3dfcf19db354d8bc5e85e47c1c7"
 }

package/assets/skills/task-completion-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Exhaustive completion discipline for long/multi-item tasks - inventory, coverage ledger, verified done.",
   "updated": "2026-06-10T22:11:09+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "6e3facba307eb2b55cefbab2e4b2a346a2b82f93c3ef47e11ebeb78c3c9453a8"
 }

package/assets/skills/technical-writing-policy/SKILL.md

@@ -37,6 +37,12 @@ microcopy - the reader shouldn't have to study it.
    order to". Plain verbs and concrete nouns instead.
 5. **Restating the heading.** A panel titled "Accounts" whose intro begins "Manage your
    accounts" wastes the first line. Add information the title does not already carry.
+6. **Over-explaining a feature.** A feature card or list item sells the outcome in one or
+   two lines, then stops. Cut the mechanism, config internals, every flag, and the edge
+   cases out of the pitch - lead with what the reader gets, name the command or show the
+   one example that proves it, and leave the rest for the docs. A landing/README feature
+   list whose job is to make the reader *want* it still obeys this: punchy beats thorough.
+   Three padded sentences hide the hook that one tight sentence would land.
 
 ## Rules
 
@@ -45,7 +51,9 @@ microcopy - the reader shouldn't have to study it.
 - Be specific over clever: "Resets Monday 11:00" beats "Resets soon".
 - Match length to the slot: a setting hint is one line; a panel/page intro is one sentence
   of orientation plus, only if needed, one of consequence (a caveat, a default, a cost).
-  An empty state is one line that invites the next action.
+  An empty state is one line that invites the next action. A feature card leads with the
+  benefit in the first clause, runs one or two sentences, and lets the command or example
+  carry the proof - never a how-it-works paragraph.
 - Active voice, present tense, sentence case. The control names the exact action ("Save
   changes", not "Submit"); the same verb survives the whole flow (Publish -> "Published").
 - Errors say what went wrong and how to fix it, in the interface's voice - never vague,

package/assets/skills/technical-writing-policy/skill.json

@@ -1,9 +1,9 @@
 {
   "name": "technical-writing-policy",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "provider": "FJRG2007/enigma",
   "description": "Concise, realistic technical copy - UI microcopy, descriptions, hints, empty/error states, and README/doc prose that informs without over-explaining or restating the obvious.",
-  "updated": "2026-06-25T17:54:55+02:00",
-  "cliVersion": "1.21.2",
-  "sha": "647a896d9e6178cd109c475aae91cb98f465c2fae5e4e1eeaab951829832ac4c"
+  "updated": "2026-06-26T14:09:06+02:00",
+  "cliVersion": "1.22.0",
+  "sha": "e750988b8de51d8a69be621673dceca5413ebad7e1a48e40acd18aad526d9928"
 }

package/assets/skills/testing-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Test strategy, coverage gates, deterministic tests, mocking discipline, regression-first bug fixing, and test-suite organization (layout by type/domain, mirrored paths, file naming, fixture/helper placement).",
   "updated": "2026-06-16T17:11:49+02:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "3bdf591057b760f674fb2b1425f63acb426cda2c4f042e1a74c5a5d3807df664"
 }

package/assets/skills/validation-policy/skill.json

@@ -4,6 +4,6 @@
   "provider": "FJRG2007/enigma",
   "description": "Strict frontend + backend schema validation, schema consistency, and safe client-facing error handling.",
   "updated": "2026-06-25T18:21:50-04:00",
-  "cliVersion": "1.21.2",
+  "cliVersion": "1.22.0",
   "sha": "50349f5b3c55cc337f828dd510c163550614832acb28714871210a7c115a1501"
 }

package/bin/checksums.json

@@ -1,6 +1,6 @@
 {
-  "enigma-darwin-arm64": "d48edd6cc80a9e06b0356f7e1bbc6fe02617d542e479645ea3d5eda7b3331a14",
-  "enigma-linux-arm64": "c78f82de2f41be12241a6022d334a65b96ddd3b79dedde55f3699a95ffda78c5",
-  "enigma-linux-x64": "f6f0009161820c77ef4952d9de3d0500fa08b80a7a42b9317f9350db37ad370b",
-  "enigma-win32-x64.exe": "78a6e95dec2e9edacb816ae24de43b63a450a262c74f5a46eb2fae0196d1f227"
+  "enigma-darwin-arm64": "d226fe46e9699ad8a5959c989881c5fe3eaef9e64790261d795a08119d7b9b10",
+  "enigma-linux-arm64": "1f0dccc3949c95b2a682db6786699ed7f305fa8f1de017018e722235fea71117",
+  "enigma-linux-x64": "7f439847944b8b15ff1fc13309789d1e65a469af62aceab1c212b2f15301d001",
+  "enigma-win32-x64.exe": "0576806e5d99cdfcd9460c7d20655e1f4b1d0d35ff1f97d3c73c243f21d02e79"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "enigma-cli",
-  "version": "1.21.2",
+  "version": "1.22.0",
   "description": "Everything you need to work with a coding agent: install shared policy skills for Claude Code, OpenAI Codex and opencode, and set up portable git security hooks.",
   "type": "module",
   "bin": {