Receber por email
← Voltar para o catálogo

build-and-test

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

56estrelas
Atualizado há 8 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add xvirobotics/metaskill

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/build-and-test/svg)](https://www.skillteca.com.br/skills/build-and-test)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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]
Compartilhar X LinkedIn