Skip to content
Back to skills

Build And Test

ASecurity

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

  • 67 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 26, 2026
code-qualitytypescriptbashgit

Security analysis

A100/100

Scanned May 27, 2026

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

Installs into .claude/skills of the current project.

Are you the author of Build And Test?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Build And Test
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/xvirobotics-build-and-test/badge)](https://www.skillsdirectory.com/skills/xvirobotics-build-and-test)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: build-and-test
description: "Install dependencies, run type checking, lint, tests, and build the project. Use after making code changes to verify nothing is broken."
user-invocable: true
context: fork
allowed-tools: Bash, Read, Grep
---

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

```bash
npm ci
```

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

### Step 2: TypeScript Type Checking

```bash
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

```bash
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

```bash
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

```bash
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]
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.