사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/c3sc0-v4113/scaffold --skill project-min-evaluation시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Project Minimum Evaluation
Activation Contract
Load this skill before reporting implementation work as complete, before committing, or when asked to verify quality.
Hard Rules
- Detect the package manager from the project; never hardcode a runner.
- Run only scripts defined in
package.jsonscripts; report expected scripts that are missing instead of inventing commands. - Run from the repository root, in the order below, and do not skip a failing step to reach a later one.
- Never claim completion while a check fails or was not run.
Decision Gates
| Project signal | Runner |
|---|---|
packageManager field in package.json | use the manager it names |
pnpm-lock.yaml | pnpm run <script> |
bun.lock or bun.lockb | bun run <script> |
package-lock.json, or no other signal | npm run <script> |
| Script | Run when |
|---|---|
lint | always, if defined |
typecheck | always, if defined |
format:check | always, if defined |
test | always, if defined |
doctor | always, if defined |
check | always, if defined (aggregate gate) |
test:e2e | only when end-to-end behavior changed |
Execution Steps
- Read
package.jsonand the lockfiles to choose the runner. - Collect the scripts from the table that exist in
scripts. - Run each existing script in table order with the chosen runner.
- Stop at the first failure, fix it, and rerun from that script.
Output Contract
Report each script as passed, failed, or not defined. For a failure or a check that cannot run, give the exact command, the exact error, and the unverified scope.
References
- references/script-discovery.md — detection edge cases.
