Agent skill · Testing & QA

build-test

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

nexu95,528★ · +2,037/wk · 5 repos on radarProfile →
claude-codecodexcursorApache-2.0
Install
npx skills add nexu-io/open-design --skill build-test --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 2 KB
Bundled scripts: none
Path: plugins/_official/atoms/build-test/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 83,577 · +1,339 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 the runner's logBudgetBytes limit, default 1 MiB) ``` The atom emits **two** signals the devloop reads: - `build.passing: boolean` — the typecheck command exited 0. - `test

What's inside
Steps it walks through
  1. Inputs
  2. Default commands by framework
  3. Output
  4. Convergence
  5. Anti-patterns the prompt fragment forbids
  6. Status
Ships with 1 file
  • open-design.json
More from open-design
All skills →
About this skill
What does the build-test skill do?

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

How do I install it?

Run `npx skills add nexu-io/open-design --skill build-test --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going