Pantheon Test Quality (Nemesis)

Review test files for coverage gaps, assertion quality, and reliability.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jschulte/pantheon --skill pantheon-test-quality-nemesis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Pantheon Test Quality (Nemesis)
Source: https://github.com/jschulte/pantheon/tree/main/src/skills/pantheon-test-quality
Command: npx skills add https://github.com/jschulte/pantheon --skill pantheon-test-quality-nemesis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need for high-quality test suites by identifying gaps in coverage, improving assertion clarity, and ensuring test reliability, thereby reducing bugs and increasing confidence in code changes.

Core Features & Use Cases

  • Coverage Analysis: Verifies that happy paths, edge cases, boundary conditions, and error scenarios are adequately tested for all public functions.
  • Assertion Quality Check: Ensures tests use specific and meaningful assertions, rather than vague checks.
  • Test Structure & Reliability: Evaluates tests for proper structure (Arrange/Act/Assert), deterministic behavior, and effective mocking.
  • Use Case: After a new feature is developed, use this Skill to automatically review all associated test files to ensure they are comprehensive, reliable, and effectively validate the new code's behavior.

Quick Start

Use the Pantheon Test Quality skill to review the test files for story key '1-3' given the changed files and sprint artifacts directory.

Frequently Asked Questions about Pantheon Test Quality (Nemesis)

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

FAQPage Schema
How do I check my test files for missing edge cases and error condition coverage?

Test coverage analysis reviews your test files to identify gaps in happy paths, edge cases, boundary conditions, and error scenarios. It requires a specific story key, file list, and sprint artifacts path to evaluate all public functions.

What's the best way to evaluate test reliability and structure for a new feature?

Evaluating test reliability involves checking tests for proper Arrange/Act/Assert structure, deterministic behavior, and effective mocking. You can review all associated test files by providing the changed files and sprint artifacts directory.

Do I need sprint artifacts and a story key to review test coverage?

Yes, test coverage reviews require a specific story key, a file list, and the sprint artifacts path for operation. These inputs allow the review process to locate and analyze the correct test files within your development sprint.

How does test structure analysis handle deterministic behavior and mocking?

Test structure analysis evaluates your tests for deterministic behavior and effective mocking by checking for proper Arrange/Act/Assert patterns. This ensures your tests run reliably and validate code behavior without flakiness.

Can I review test files for assertion quality and coverage gaps in a software sprint?

Yes, you can review test files for coverage gaps and assertion quality within a software development sprint. This process identifies missing tests for error conditions and evaluates assertion specificity using your provided file list and sprint artifacts.