roli-lpci/quick-gate-js / skills/quick-gate-js
quick-gate-js
VerifiedRun the optional KWIK-E-GATE JS/TS adapter or interpret its gate-result/v1 diagnostics. Use for JavaScript/TypeScript tool checks; the core owns completion receipts.
Quick Gate is the optional JS adapter for KWIK-E-GATE. The core owns content-bound completion receipts; this package also supports standalone Node users.
Quick Gate runs the checks a JavaScript/TypeScript project already defines
as one gate and emits a validated gate-result/v1 result
(https://github.com/hermes-labs-ai/quick-gate-js). It coordinates ESLint,
tsc, the build, and Lighthouse; it does not replace them or prove the code
correct.
Run it
- This skill describes the unreleased 0.4.0 source candidate. Use an explicitly
installed
quick-gateor the checkout'snode /path/to/src/cli.js; verify its version. After publication the exact install pin isquick-gate@0.4.0. Do not download packages implicitly. Published 0.3.2 remains compatible for evaluation; use--deterministic-onlyfor its repair behavior. - Make sure the project's own dependencies are installed. Quick Gate calls
fallbacks with
npx --no-installand never installstscorlhcifor you. - From the project root, write the changed files (newline-delimited or a
JSON array) and run with an explicit mode and an external output directory:
printf 'src/app.ts\n' > "$TMPDIR/qg-changed.txt" npx --no-install quick-gate run --mode quick \ --changed-files "$TMPDIR/qg-changed.txt" \ --output-dir "$(mktemp -d)"--modeand--changed-filesare required.quickruns lint, typecheck, and Lighthouse;fullalso runs build. Checks use the project'slint,typecheck,build, andlighthouse/ci:lighthousenpm scripts, thencommandsinquick-gate.config.json, then fallbacks (npx --no-install tsc --noEmit;npx --no-install lhci autorun, which needs--output-dir). - Stdout is JSON:
{ status, gateResult, artifacts, runId }. The output directory holdsfailures.json,run-metadata.json(command traces with the underlying tool output), andgate-result.json.
Read the verdict exactly
- Exit code
0only when the gate passes;1otherwise, including usage errors. - Top-level
statusispassorfail. It isfailwhenevergateResult.statusis anything other thanpass. gateResult.schemaisgate-result/v1.gateResult.statusis one of:pass: every enabled check ran and passed with no findings.fail: checks ran and at least one produced a finding.timeout: a check timed out.error: a check could not run (missingcommand, start error, or Lighthouse fallback without an output directory), or the checked files changed during the run. Precedence: changed input, thentimeout, thenmissing/error, then findings, thenpass.
- Per-check
statusispass,fail,timeout,missing,error, orskipped(buildinquickmode). - Release 0.4.0 has no
unknownresult status. Reporttimeoutanderroras "not verified". They are not a pass and not proof of a code defect.
Release 0.4.0 limits
- Lighthouse is enabled in both modes by default. Disable an inapplicable
check only with an explicit boolean under
gatesinquick-gate.config.json; disabled checks are recorded asskipped. Disclose skipped checks instead of presenting them as verified. - Repair is separate from evaluation and defaults to deterministic in 0.4.0.
--model-assistedexplicitly opts into local Ollama. Runquick-gate repaironly when in scope. It can modify project files. After a repair, reviewgit diffand the report. - Artifacts can contain command output and paths. Do not upload them anywhere the user has not approved.
Fixtures
fixtures/clean and fixtures/broken in this skill directory are two tiny
TypeScript packages. They are the same except for one type error in
broken/greeting.ts. Each declares a no-op Lighthouse command because it is
not a web app. To check that the skill works, copy one fixture to a temp
directory and run:
npm install --ignore-scripts --no-audit --no-fund --no-package-lock
npx --no-install quick-gate run --mode quick --changed-files changed-files.txt --output-dir "$(mktemp -d)"
The bundled fixtures are expected to produce these results with quick-gate 0.4.0:
cleanexits0:status: pass. Checks are lintpass, typecheckpass, buildskipped, lighthousepass, with 0 findings.brokenexits1:status: fail. Typecheck isfail(exit 2) with findingtypecheck_failure, and the tsc error is inrun-metadata.jsontraces.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |