How do I install the Build And Test skill?

Run npx skillmds@latest add diegosouzapw/build-and-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Build And Test safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Build And Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Build And Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Build And Test?

diegosouzapw (@diegosouzapw) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Build And Test by diegosouzapw — Agent Skill

Name: Build And Test
Rating: 4.2 (5 reviews)
Author: diegosouzapw

File contents

Build & Test — Phoenix Agentic Website Frontend (Next.js)

Mandatory first step: terminal scope check

Before build/test commands, verify terminal scope:

Set-Location "C:\Users\rivie\vsCodeProjects\Phoenix-Agentic-Website-Frontend"
Get-Location
git rev-parse --show-toplevel
git branch --show-current

If scope is wrong, open a fresh Website Frontend-scoped terminal and retry.

Repo Identity

This is the public website frontend. Next.js app with TypeScript, React, and Tailwind CSS.

Quick Commands

Task label	Command	Purpose
`website: dev: setup`	`npm install`	Install dependencies
`website: dev: run`	`npm run dev`	Start dev server
`website: dev: lint`	`npm run lint`	Run ESLint
`website: dev: typecheck`	`npm run typecheck`	Run tsc --noEmit
`website: dev: test`	`npm run test`	Run vitest
`website: dev: build`	`npm run build`	Production build
`website: dev: check`	lint + typecheck + test + build	Full validation
`website: dev: clean`	Remove .next, coverage, dist	Clean artifacts

Using VS Code Tasks

Prefer using run_task or create_and_run_task to execute these tasks. Task IDs:

shell: website: dev: setup
shell: website: dev: run
shell: website: dev: lint
shell: website: dev: typecheck
shell: website: dev: test
shell: website: dev: build
shell: website: dev: check
shell: website: dev: clean

Manual Commands (if needed)

# Install
npm install

# Lint
npm run lint

# Typecheck
npm run typecheck

# Test
npm run test

# Build
npm run build

Validation checklist

Lint passes — npm run lint
Typecheck passes — npm run typecheck
Tests pass — npm run test
Build succeeds — npm run build
Full check — npm run lint; npm run typecheck; npm run test; npm run build

Testing rules

Tests must be deterministic — no network calls, no randomness without seed control
Use vitest for all tests
Always run full check before considering work complete

Common issues

Error	Fix
`npm ci` failure	Delete `node_modules` and `package-lock.json`, run `npm install`
ESLint errors	Run `npm run lint` and fix violations
TypeScript errors	Run `npm run typecheck` locally
Next.js build failure	Check for SSR-incompatible imports
Test failure	Run `npm run test` locally, check assertions

---name: build-and-testdescription: Build, test, lint, and validate the Phoenix Agentic Website Frontend. Use when user asks to build, compile, test, lint, run checks, fix test failures, or validate changes in the Website Frontend repo.---# Build & Test — Phoenix Agentic Website Frontend (Next.js)## Mandatory first step: terminal scope checkBefore build/test commands, verify terminal scope:1. `Set-Location "C:\Users\rivie\vsCodeProjects\Phoenix-Agentic-Website-Frontend"`2. `Get-Location`3. `git rev-parse --show-toplevel`4. `git branch --show-current`If scope is wrong, open a fresh Website Frontend-scoped terminal and retry.## Repo IdentityThis is the **public website frontend**. Next.js app with TypeScript, React, and Tailwind CSS.## Quick Commands| Task label | Command | Purpose ||------------|---------|---------|| `website: dev: setup` | `npm install` | Install dependencies || `website: dev: run` | `npm run dev` | Start dev server || `website: dev: lint` | `npm run lint` | Run ESLint || `website: dev: typecheck` | `npm run typecheck` | Run tsc --noEmit || `website: dev: test` | `npm run test` | Run vitest || `website: dev: build` | `npm run build` | Production build || `website: dev: check` | lint + typecheck + test + build | Full validation || `website: dev: clean` | Remove .next, coverage, dist | Clean artifacts |## Using VS Code TasksPrefer using `run_task` or `create_and_run_task` to execute these tasks. Task IDs:- `shell: website: dev: setup`- `shell: website: dev: run`- `shell: website: dev: lint`- `shell: website: dev: typecheck`- `shell: website: dev: test`- `shell: website: dev: build`- `shell: website: dev: check`- `shell: website: dev: clean`## Manual Commands (if needed)```bash# Installnpm install# Lintnpm run lint# Typechecknpm run typecheck# Testnpm run test# Buildnpm run build```## Validation checklist1. **Lint passes** — `npm run lint`2. **Typecheck passes** — `npm run typecheck`3. **Tests pass** — `npm run test`4. **Build succeeds** — `npm run build`5. **Full check** — `npm run lint; npm run typecheck; npm run test; npm run build`## Testing rules- Tests must be deterministic — no network calls, no randomness without seed control- Use vitest for all tests- Always run full check before considering work complete## Common issues| Error | Fix ||-------|-----|| `npm ci` failure | Delete `node_modules` and `package-lock.json`, run `npm install` || ESLint errors | Run `npm run lint` and fix violations || TypeScript errors | Run `npm run typecheck` locally || Next.js build failure | Check for SSR-incompatible imports || Test failure | Run `npm run test` locally, check assertions |

Frequently asked questions

Build And Test