domains / families / software-engineering / grade-tests

grade-tests

separate

Grade curated individual tests for readiness, A-F quality and improvements. ALWAYS USE FOR: grade tests, review only a named test, per-test readiness or quality bands for supplied methods, bodies, file spans or bounded PR diffs, including existing tests. Return Pass/Failed/Uncertain/Not applicable; unresolved/empty scopes omit grades. Compose read-only per-test evidence. Polyglot. DO NOT USE FOR: suite audits (test-engineer/test-anti-patterns), concrete fix/feature detection proof (test-value-evidence), writing/fixing tests, or coverage.

When to use

• A PR automation workflow needs to post a decision on the tests introduced or
• A reviewer has a specific list of tests (a file, a class, a method list,
• A maintainer wants to triage which of N tests in a contribution deserve

When not to use

• The caller wants a full suite audit or comparative metrics — use
• The caller wants to *write* new tests — use `test-engineer`
• The caller wants to measure code coverage or CRAP scores — use
• The caller wants to fix issues directly in test code — invoke the
• No specific list of tests is provided. Do **not** try to grade every test

Skill page

Source