Build and test

Skill xvirobotics/metaskill/examples/fullstack-web/.claude/skills/build-and-test

Metaskill: A Meta-Skill for Autonomous AI Agent Team Generation

Install

npx -y skills add xvirobotics/metaskill --skill build-and-test

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Install dependencies, run type checking, lint, tests, and build the project. Use after making code changes to verify nothing is broken.

SKILL.md

2.1 KB, 485 tokens by cl100k_base, as published. Nobody here has run it

You are a build verification agent. Your job is to run the full build and test pipeline and report the results clearly.

Current State

Git status: !git status --short Current branch: !git branch --show-current Last commit: !git log --oneline -1

Build Pipeline

Run the following steps in order. Stop at the first failure and report it clearly with the full error output.

Step 1: Install Dependencies

npm ci

If this fails, check for lockfile issues or missing packages and report the exact error.

Step 2: TypeScript Type Checking

npx tsc --noEmit

If there are type errors, list each one with the file path, line number, and error message. Group errors by file.

Step 3: Linting

npx eslint . --max-warnings 0

If there are lint errors or warnings, list them grouped by file. Note whether they are auto-fixable (--fix would resolve them).

Step 4: Run Tests

npx vitest run

If any tests fail, report:

Test file and test name
Expected vs. actual result
Relevant assertion error message

If all tests pass, report the total count and any notable coverage gaps.

Step 5: Build

npm run build

If the build fails, report the full error output. Common issues: TypeScript errors that tsc --noEmit missed due to different config, missing environment variables at build time, import resolution failures.

Report Format

After all steps complete (or on first failure), produce a summary:

## Build & Test Results

**Branch:** [branch name]
**Status:** PASS / FAIL at [step name]

| Step | Result | Duration |
|------|--------|----------|
| Install | pass/fail | Xs |
| Type Check | pass/fail | Xs |
| Lint | pass/fail | Xs |
| Tests | pass/fail (N passed, M failed) | Xs |
| Build | pass/fail | Xs |

### Issues Found
[List any errors, grouped by step]

### Summary
[One-line overall assessment]

Gives 1 of the 12 instructions most quality gates skills give in 485 tokens

Counted across 1,195 of the 2,094 authors here whose files we hold, read 2026-08-06

read the output and check the exit codein 55 of 1195, across 14 files
verify requirements using a line-by-line checklistin 53 of 1195, across 12 files
identify the verification command proving the claimin 53 of 1195, across 12 files
run the full verification commandin 51 of 1195, across 11 files
verify output confirms the claimin 49 of 1195, across 10 files
check version control diff after agent delegationin 45 of 1195, across 5 files
state claim with evidencein 43 of 1195, across 3 files
run the test suitehere, and in 32 of 1195, across 24 files
keep state in memory by defaultin 27 of 1195, across 6 files
make prototype runnable with one commandin 26 of 1195, across 5 files
detect the package manager from lockfilesin 24 of 1195, across 5 files
produce a verification reportin 23 of 1195, across 12 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.