Skip to content

egregore-labs/egregore / .codex/skills/test

Run Egregore's fast static, Runtime-contract, and targeted automated test gate before save. Optional relationship index validation requires an explicit request.

Egregore test Adapter

This adapter runs the canonical Egregore workflow for test. Its one maintained body is .claude/skills/test/SKILL.md; read that file completely and follow it here.

Use the project shell and filesystem directly. Do not invoke Claude Code commands. Translate interactive choices to structured Codex question tooling when it is available; otherwise render compact numbered choices with an Other: option and wait for the user.

Structured UX parity

This workflow has a Claude skill with user-visible structured output. After reading .claude/skills/test/SKILL.md, reproduce the same visible UX in Codex:

  • Preserve TUI boxes, markdown tables, rich cards, browser artifact rendering, exact confirmation blocks, and "no preamble" rules from the source skill.
  • Use the source skill's frame width, section order, labels, status footer, and examples as the contract for the final response.
  • Never replace a required box/table/card/artifact view with a prose summary unless the user explicitly asks for a summary.
  • When the source says to output a TUI box directly, paste that box as the visible response, preferably in a text fenced block.
  • If the canonical body says the command's stdout is the card and must not be repeated, that rule assumes a host that displays command output in full; in Codex, paste the card once as the visible response in a text fenced block and do not print it a second time.
  • Never show raw JSON, raw command output, or unformatted script output when the source skill requires formatted status or rendered output.
  1. Read .claude/skills/test/SKILL.md for the workflow details.
  2. Run the referenced bin/ scripts directly from Codex.
  3. Treat graph and publish steps as best-effort unless that workflow explicitly says they are required.
  4. For every external notification, follow .claude/context/notification-consent.md: plan without sending, then show a separate exact Send / Edit / Cancel checkpoint. Never infer notification consent from the workflow request or a batch approval.
  5. Keep local-mode behavior filesystem-first and avoid graph or notification calls when egregore.json declares "mode": "local".
  6. Never call the deprecated egregore-handoff CLI for Egregore project handoffs.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall