build-test

Included with Lifetime

$97 forever

Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.

Code Review

What this skill does


# Build test

Spec §20.2 / §22.4: the "subjective `critique-theater` panel" is
not enough on its own — a code-migration / tune-collab run must
prove the build still passes. This atom shells out to the
project's declared test commands and emits structured signals the
devloop's `until` evaluator reads.

## Inputs

- The active target stack (recorded in `code/index.json` +
  `plan.md`'s targetStack block).
- The user's optional override (`od plugin run --input
  testCommand='pnpm test'`).

## Default commands by framework

| framework | typecheck | test |
| --- | --- | --- |
| next | `pnpm typecheck` | `pnpm test` |
| vite | `pnpm typecheck` | `pnpm test` |
| remix | `pnpm typecheck` | `pnpm test` |
| custom | (read from `package.json.scripts`) | (read from `package.json.scripts`) |

## Output

```text
project-cwd/
└── critique/
    ├── build-test.json   # { build: 'passing' | 'failing', tests: 'passing' | 'failing' | 'skipped', durationMs, commandsRun: [...], failures: [...] }
    └── build-test.log    # raw stdout / stderr (truncated to OD_BUILD_TEST_LOG_BUDGET_BYTES, default 1 MiB)
```

The atom emits **two** signals the devloop reads:

- `build.passing: boolean` — the typecheck command exited 0.
- `tests.passing: boolean` — the test command exited 0.

Plus the legacy `critique.score` so existing pipelines that read
the score keep working: 5 when both pass, 3 when only build
passes, 1 when both fail.

## Convergence

Pipelines wire the atom into a devloop:

```jsonc
{
  "id": "verify",
  "atoms": ["patch-edit", "build-test"],
  "repeat": true,
  "until": "(build.passing && tests.passing) || iterations >= 8"
}
```

## Anti-patterns the prompt fragment forbids

- Running tests on a partially-edited working tree (the atom
  always runs after `patch-edit`, and only when `plan.steps`'s
  current step is in `completed` state).
- Suppressing test failures by changing test files; that violates
  the rewrite-plan ownership rule.
- Setting `tests: 'skipped'` without a non-empty `reason` field.

## Status

Reserved id, prompt-only fragment in v1. The shell-out wrapper +
log-truncation worker land in spec §16 Phase 7.

Files: 2

Size: 3.2 KB

Complexity: 12/100

Category: Code Review

Source: https://github.com/nexu-io/open-design/tree/main/plugins/_official/atoms/build-test

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts