grade-tests

Grades a curated list of test methods and outputs a per-test letter-grade table for PR comments.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/Netcodr81/kinetic-reports --skill grade-tests-netcodr81
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: grade-tests
Source: https://github.com/Netcodr81/kinetic-reports/tree/main/.github/skills/grade-tests
Command: npx skills add https://github.com/Netcodr81/kinetic-reports --skill grade-tests-netcodr81

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewers of a pull request need a quick per-test verdict on the tests that PR adds or changes, but full suite-audit reports are too long to post as a PR comment. This Skill grades each specified test method individually and produces a compact table mapping every test to a letter grade (A–F), a score band, and a one-line note. ## Core Features & Use Cases - Per-Test Grading: Scores each test on three sub-dimensions — assertion strength, structure & focus, and anti-pattern hygiene — then combines them into a capped overall letter grade with a score band. - Polyglot Support: Works across .NET, Python, TypeScript/JavaScript, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++ by loading language-specific extension guidance before scoring. - PR-Comment Output: Produces a short summary plus a markdown table (capped at 50 rows with collapsed overflow) suitable for posting directly as a pull request comment. - Use Case: A CI workflow lists the tests modified in a PR; the Skill grades each one and posts a table showing which new tests are solid and which need follow-up improvements. ## Quick Start Grade the test methods in OrderTests.cs and produce a per-test grade table I can post as a PR comment.

Frequently Asked Questions about grade-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I grade the tests changed in a pull request?▼

Provide the Skill with the list of changed test methods, the file paths containing them, or the PR diff. It resolves each test body, scores assertion strength, structure, and anti-patterns, then outputs a markdown table with letter grades and notes suitable for a PR comment.

What test frameworks and languages does per-test grading support?▼

It supports .NET (MSTest, xUnit, NUnit, TUnit), Python (pytest), TypeScript/JavaScript (Jest, Vitest), Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, and C++. Language-specific extension files define the assertion APIs and idiomatic patterns used during scoring.

How is the overall test grade calculated?▼

Each test gets three sub-grades: assertion strength (45%), anti-pattern hygiene (30%), and structure (25%). The weighted average maps to a letter grade and score band, but the overall grade is capped at the worst sub-grade, so any F sub-grade forces an overall F.

When should I not use per-test grading?▼

Do not use it for full suite audits, writing new tests, fixing failures, or measuring code coverage. Use a test-quality-auditor or test-anti-patterns analysis for suite-wide reports, and a test-generation tool for authoring new tests.

Why was my request to grade tests rejected?▼

The Skill rejects ambiguous requests with no explicit scope, such as "grade my tests" with no list. Provide an explicit list of fully-qualified test method names, file paths with an instruction to grade all tests in them, or a diff hunk identifying the changed tests.

Are exception-only tests penalized for having few assertions?▼

No. Exception assertions such as Assert.ThrowsException, pytest.raises, or expect(fn).toThrow are treated as complete on their own. The Skill also counts mock verifications and bare assertion forms like pytest assert and Go if got != want checks as real assertions.