使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/c3sc0-v4113/scaffold --skill project-min-evaluation開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
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.
