القائمة
Laboratory CI gate audit and verification workflow. Use when checking whether experiment, harness, analysis, docs, or Spellbook harness changes are safe to ship. Trigger: /ci, /gates.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Assess and improve codebase readiness for AI coding agents. Dispatches parallel subagents to evaluate style, testing, docs, architecture, CI, observability, security, and dev environment. Produces a scored report with prioritized remediation. Then executes the highest-impact fixes. Use when: "agent readiness", "is this codebase agent-ready", "readiness report", "make this codebase agent-friendly", "agent-ready assessment", "readiness audit", "prepare for agents". Trigger: /agent-readiness, /readiness.
Dialectical premise-and-alternatives audit for a plan, spec, or context packet. Four moves: premise challenge (is this the right problem?), mandatory structurally-distinct alternatives, cross-model outside voice, user-ratified convergence. Operationalizes the AGENTS.md "Diverge Before You Converge" doctrine at the plan-review stage. Use when: about to commit to a plan/spec/design, reviewing a ticket before shape, when "is this the right problem" would be useful, or any time a proposal smells like a symptom fix instead of a root-cause fix. Trigger: /ceo-review, /challenge, /premise-check.
Parallel multi-agent review for Laboratory changes. Prioritizes correctness, scientific validity, provenance, tests, and harness fit. Trigger: /code-review, /review, /critique.
Take one Laboratory backlog item to merge-ready. Composes /shape, /implement, /code-review, /ci, /refactor, and /qa as needed. Stops before merge. Trigger: /deliver.
Capture and share what changed — every app has a demo path; the format depends on the change and the audience. The spectrum runs from a release-notes blurb ("no demo needed, here's what moved") through a curl + JSON paste, a terminal recording, a screenshot, a GIF, up to a polished narrated launch video. Pick the path that fits the change shape (UI / API / CLI / library / agent tool / internal-only), the audience (PR reviewer / team Slack / external customer), and the time budget. Also scaffolds a project-local demo skill for repos with recurring polished-capture needs. Use when: "make a demo", "generate demo", "record walkthrough", "launch video", "PR evidence", "upload screenshots", "demo artifacts", "make a video", "demo this feature", "create a walkthrough", "show what changed", "paste the output", "release notes blurb", "scaffold demo", "generate demo skill". Trigger: /demo.
Investigate, audit, triage, and fix. Systematic debugging, incident lifecycle, domain auditing, and issue logging. Four-phase protocol: root cause → pattern analysis → hypothesis test → fix. Use for: any bug, test failure, production incident, error spikes, audit, triage, postmortem, "diagnose", "why is this broken", "debug this", "production down", "is production ok", "audit stripe", "log issues". Trigger: /diagnose.
| name | ci |
| description | Laboratory CI gate audit and verification workflow. Use when checking whether experiment, harness, analysis, docs, or Spellbook harness changes are safe to ship. Trigger: /ci, /gates. |
| argument-hint | [--audit-only|--run-only] [paths] |
make ci-smoke is the load-bearing gate in this repository. It runs Python
compile checks, compatibility-wrapper checks, unit tests, and analysis smoke
commands over committed datasets.
Do not invent a second CI owner here. If the current change needs a new
executable path verified, add that path to make ci-smoke or name it
explicitly as unverified.
make ci-smoke.--audit-only: inspect gate coverage and report gaps; do not run commands.--run-only: run make ci-smoke and report the result.git status --short and the changed paths.make check or covered by tests.make check-wrappers.make smoke-analyze or a focused test.make ci-smoke plus link/path sanity is enough.make ci-smoke
If it fails, diagnose the first failing gate from the output. Fix mechanical format/import/path issues directly when the cause is clear. Do not lower a gate or remove a test to get green.
Return:
PASS, FAIL, or UNVERIFIED