c3sc0-v4113/scaffold

project-min-evaluation

Trigger: done, complete, finish, before commit, quality check, verify.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/c3sc0-v4113/scaffold --skill project-min-evaluation

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Project Minimum Evaluation

Activation Contract

Load this skill before reporting implementation work as complete, before committing, or when asked to verify quality.

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.

Decision Gates

Project signalRunner
packageManager field in package.jsonuse the manager it names
pnpm-lock.yamlpnpm run <script>
bun.lock or bun.lockbbun run <script>
package-lock.json, or no other signalnpm run <script>
ScriptRun when
lintalways, if defined
typecheckalways, if defined
format:checkalways, if defined
testalways, if defined
doctoralways, if defined
checkalways, if defined (aggregate gate)
test:e2eonly when end-to-end behavior changed

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.

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

Related by task

from this repository

More skills

All skills