Dev run tests

Intelligence pack for software engineering based on Ainova Systems best practices

Install

npx -y skills add ainova-systems/intelligence-dev-packs --skill dev-run-tests

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

Copied from the file, not written here

Run typecheck, lint, and tests with the right scope; analyze failures

2.0 KB, as published. Nobody here has run it

Cheapest-first verification with scope detection. Invoke per task slice, at phase boundaries, and before push.

Resolve commands: profile verify set - run exactly that single gate-runner command and report what it ran and skipped; the remaining steps are its internals and this skill adds only the failure analysis. Else profile typecheck / lint / test; else detect (package.json scripts, *.sln - dotnet test, pyproject.toml - pytest, go.mod - go test ./..., Makefile targets). Confirm detected commands in one line on the first run.
Detect scope: git status --porcelain + git diff --name-only - map changed files to their test areas. Docs/markdown-only change - report "no tests to run" and stop. An explicit argument overrides.
Typecheck first - it fails fastest. On error: report the file and the first error, STOP.
Lint second. On error: report the finding, STOP.
Tests: scoped by default; full suite when shared code changed, at phase boundaries, and before push. Enforce the profile coverage_gate when set.
On failure: failing test name, the assertion, trimmed relevant output; classify the cause (production change / the test itself / environment); propose the fix. Re-run after fixes with the same scope discipline.
Report per area: pass/fail counts, duration, coverage vs the gate.

All gates green for the declared scope, or a precise failure analysis delivered - never "mostly passing".

Fixing production code - the executing skill/subagent; CI-level failures - git-finalize-pr.

Never modify tests, configs, or thresholds to make a failing gate pass.
A flaky test (passes on rerun) is reported as flaky with evidence; never silently retried into green.
Missing env/dependency - report the precondition; never stub the environment to force a pass.