agentsclimarketplace
Sign in

Testing implementation

Skill JeremyMorgan/code-review-skills/skills/testing-implementation

Evaluates test implementation and coverage, identifying gaps, weak assertions, and untested paths. Use when auditing test quality, coverage, or testing strategy.From its SKILL.md

Install
npx -y skills add JeremyMorgan/code-review-skills --skill testing-implementation

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

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

What its file declares

Copied from the file, not written here

The file declares its own license as CC0-1.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.6 KB, as published. Nobody here has run it

Target: $ARGUMENTS

If no target path is given above, review the entire codebase.

Evaluate testing implementation for this software project

Analyze:

  1. TEST COVERAGE

    • Unit test coverage percentage
    • Integration test presence
    • E2E test coverage
    • Uncovered critical paths

  2. TEST QUALITY

    • Test naming clarity
    • Arrange-Act-Assert pattern
    • Test independence
    • Mock usage appropriateness
    • Test data management

  3. TEST PATTERNS

    • Test pyramid adherence (unit > integration > E2E)
    • Testing anti-patterns (testing implementation vs behavior)
    • Brittle tests identification
    • Test speed issues

  4. MISSING TESTS

    • Error scenarios
    • Edge cases
    • Security tests
    • Performance tests

Provide a test improvement plan with examples.

Provide:

A structured finding report

A scale of 1/10 on how important each finding is

Remediation: precise code-level fix or config change (snippets welcome) if possible

Constraints & style:

Be concrete and cite exact code locations and identifiers.

Prefer minimal, drop-in fix snippets over prose.

Do not invent files or functions that aren’t present; if context is missing, mark as Unable to verify and say what code would prove it.

Write this into a markdown file and place it in the audits/ folder.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.