Skills Guide

Gate Build - Compilation validation

VerifiedCaution

Runs the build and test commands defined in `.specwright/config.json`. Captures stdout and exit codes, writing an evidence report. Returns PASS only if both commands exit 0; otherwise FAIL. Internal gate invoked by verify to confirm the codebase compiles and tests pass before proceeding.

Download and use
Sby Skills Guide Bot
TestingIntermediate
6/2/2026
Claude Code
#build#test#gate#ci#verification

Recommended for

Claude CodeTest generationQA / test engineer

Automated summary

Runs configured build and test commands, captures output, and determines whether the code compiles and tests pass.

Strengths

  • Automated and reproducible build/test verification
  • Captures evidence in a structured report file
  • Handles missing commands and timeouts with appropriate statuses

Limitations

  • Requires prior configuration in config.json
  • Only supports single commands (no complex pipelines)
  • Error output can be lengthy and hard to parse
When to use it

Use this gate after code modifications to ensure the project still builds and tests pass.

When not to use it

Do not use for checks requiring human judgment or validations unrelated to building and testing.

Security analysis

Caution
Quality score85/100

The skill executes build and test commands defined in a config file using Bash, which could be abused if the configuration is compromised. However, it is intended as an internal gate and does not directly prompt for destructive or exfiltration actions.

Findings
  • •Runs user-configurable shell commands via Bash; potential code injection if config.json is tampered with.
  • •Uses Bash, a powerful tool that can execute arbitrary commands.
How this analysis is made

Examples

Run build and test verification
Verify the build and tests to ensure the project compiles and all tests pass.
Check build only
Run the build gate to check if the code compiles, but skip the tests.
Check specific test suite
Execute the test command defined in config to confirm the unit tests pass.

name: gate-build description: >- Runs configured build and test commands. Captures output as evidence. Returns PASS if commands exit 0, FAIL otherwise. Internal gate — invoked by verify, not directly by users. allowed-tools:

  • Read
  • Bash
  • Glob
  • Write

Gate: Build

Goal

Confirm the codebase compiles and tests pass. This is the most basic gate — if the code doesn't build or tests don't pass, nothing else matters.

Inputs

  • .specwright/config.json -- commands.build and commands.test
  • .specwright/state/workflow.json -- current work unit for evidence path

Outputs

  • Evidence file at {currentWork.workDir}/evidence/build-report.md
  • Gate status update in workflow.json: PASS, FAIL, or ERROR
  • Console output showing results inline (users see findings, not just badges)

Constraints

Execution (LOW freedom):

  • Read build command from config.json commands.build. Run it. Capture output.
  • Read test command from config.json commands.test. Run it. Capture output.
  • If a command is null/missing, SKIP that check (not FAIL).
  • If both commands are null, gate status is SKIP.
  • Timeout: 5 minutes per command. If exceeded, status is ERROR.

Verdict (LOW freedom):

  • Follow protocols/gate-verdict.md for verdict rendering.
  • Build exit code 0 + test exit code 0 = PASS.
  • Any non-zero exit code = FAIL.
  • Show failing output inline so the user sees what broke.

Evidence (LOW freedom):

  • Follow protocols/evidence.md for file format and storage.
  • Write evidence file with: command run, exit code, stdout/stderr, timestamp.
  • Update workflow.json gates section per protocols/state.md.

Protocol References

  • protocols/gate-verdict.md -- default-FAIL, self-critique, visibility
  • protocols/evidence.md -- evidence storage and freshness
  • protocols/state.md -- gate status updates

Failure Modes

| Condition | Action | |-----------|--------| | Build command not configured | SKIP build check, continue to test check | | Test command not configured | SKIP test check | | Both commands null | Gate status = SKIP | | Command times out (>5min) | Gate status = ERROR with timeout message |

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/gate-build-compilation-validation-mm78nnrd/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/gate-build-compilation-validation-mm78nnrd' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/gate-build-compilation-validation-mm78nnrd/download' --output '.skill-downloads/gate-build-compilation-validation-mm78nnrd/SKILL.md.part' && mv '.skill-downloads/gate-build-compilation-validation-mm78nnrd/SKILL.md.part' '.skill-downloads/gate-build-compilation-validation-mm78nnrd/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/gate-build-compilation-validation-mm78nnrd/SKILL.md' && test -s '.skill-downloads/gate-build-compilation-validation-mm78nnrd/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/gate-build' && cp -R '.skill-downloads/gate-build-compilation-validation-mm78nnrd' '.claude/skills/gate-build'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/gate-build-compilation-validation-mm78nnrd'

openskills read 'gate-build-compilation-validation-mm78nnrd'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/gate-build-compilation-validation-mm78nnrd/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

ClickHouse Performance Comparison

Testing

Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.

Claude CodeintermediateSafe 49,547
Skills Guide Bot

Analyze CI Performance Reports

Testing

Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.

Claude CodeintermediateSafe 49,516
Skills Guide Bot

Santa Method

Testing

Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.

Claude CodeCodexCursorintermediateSafe 244,766
Skills Guide Bot