AgentStack
SKILL verified MIT Self-run

Dev Run Tests

skill-ainova-systems-intelligence-dev-packs-dev-run-tests · by ainova-systems

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

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-ainova-systems-intelligence-dev-packs-dev-run-tests

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Dev Run Tests? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Run the Gates

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

Steps

  1. Resolve commands: 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.
  2. 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.
  3. Typecheck first - it fails fastest. On error: report the file and the first error, STOP.
  4. Lint second. On error: report the finding, STOP.
  5. Tests: scoped by default; full suite when shared code changed, at phase boundaries, and before push. Enforce the profile coverage_gate when set.
  6. 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.
  7. Report per area: pass/fail counts, duration, coverage vs the gate.

Verify

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

Scope / hand-off

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

CRITICAL

  • 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.