Skip to main content

build-and-test

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

소스 정보

저장소
xvirobotics/metaskill
최근 소스 활동
2026년 2월 23일 03:44
감지된 SKILL.md 언어
영어
스타
71
포크
10

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

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] ```
GitHub에서 보기