project-min-evaluation

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Project Minimum Evaluation

项目最低评估

Activation Contract

激活契约

Load this skill before reporting implementation work as complete, before committing, or when asked to verify quality.
在报告实现工作完成之前、提交之前,或被要求验证质量时,加载此skill。

Hard Rules

硬性规则

  1. Detect the package manager from the project; never hardcode a runner.
  2. Run only scripts defined in
    package.json
    scripts
    ; report expected scripts that are missing instead of inventing commands.
  3. Run from the repository root, in the order below, and do not skip a failing step to reach a later one.
  4. Never claim completion while a check fails or was not run.
  1. 从项目中检测包管理器;绝不硬编码运行器。
  2. 仅运行
    package.json
    的
    scripts
    中定义的脚本;对于缺失的预期脚本,应报告缺失,而非自行发明命令。
  3. 从仓库根目录按以下顺序运行,且不要为了到达后续步骤而跳过失败的步骤。
  4. 当检查失败或未运行时,绝不宣称完成。

Decision Gates

决策门

Project signalRunner
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>
ScriptRun 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
项目信号运行器
package.json
中的
packageManager
字段
使用其指定的管理器
pnpm-lock.yaml
pnpm run <script>
bun.lock
或
bun.lockb
bun run <script>
package-lock.json
,或没有其他信号
npm run <script>
脚本运行时机
lint
如果定义,始终运行
typecheck
如果定义,始终运行
format:check
如果定义,始终运行
test
如果定义,始终运行
doctor
如果定义,始终运行
check
如果定义,始终运行(聚合门)
test:e2e
仅当端到端行为发生变化时运行

Execution Steps

执行步骤

  1. Read
    package.json
    and the lockfiles to choose the runner.
  2. Collect the scripts from the table that exist in
    scripts
    .
  3. Run each existing script in table order with the chosen runner.
  4. Stop at the first failure, fix it, and rerun from that script.
  1. 读取
    package.json
    和锁文件以选择运行器。
  2. 收集表中存在于
    scripts
    中的脚本。
  3. 使用所选运行器按表顺序运行每个存在的脚本。
  4. 在第一次失败时停止,修复它,并从该脚本重新运行。

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.
  • references/script-discovery.md — 检测边界情况。