skills.rest
SeventeenthEarth
SeventeenthEarthCOMMUNITY
Explore all skills by this author →
GitHub

17th-test-analyzer

Compare staged changes against TASK.md to generate a coverage gap report.

Updated Jan 23, 2026
Search Tags:#codex#analyze#gpt-5.2#test-coverage#staged-changes#TASK.md#pre-pr
One-click install
npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-test-analyzer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 17th-test-analyzer
Source: https://github.com/SeventeenthEarth/glm-worker-mcp/tree/main/skills/17th-test-analyzer
Command: npx skills add https://github.com/SeventeenthEarth/glm-worker-mcp --skill 17th-test-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps software teams quickly identify gaps between code changes and the task specification, ensuring testing aligns with requirements.

Core Features & Use Cases

  • Test coverage analysis: Compare staged changes against TASK.md to reveal missing tests and edge-case coverage.
  • Pre-PR validation: Use before merging to catch gaps in happy-path and edge-case scenarios.
  • Use Case: Imagine you have a new feature with changes touching multiple modules; this skill highlights untested paths and suggests targeted tests.

Quick Start

Invoke the test-analyzer on the staged changes to compare them with TASK.md and generate a coverage gap report.

Frequently Asked Questions about 17th-test-analyzer

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

FAQPage Schema
How do I check test coverage against task specifications before creating a PR?▼

To check test coverage against task specifications before a PR, analyze staged changes against TASK.md to identify missing tests for both happy paths and edge cases. This generates a report of coverage gaps and recommendations.

What is the best way to find untested code paths in staged changes?▼

Finding untested code paths in staged changes involves comparing the codebase against the task specification. This comparison highlights untested paths and suggests targeted tests to align implementation with requirements.

How does comparing tests with TASK.md improve pre-PR validation?▼

Comparing tests with TASK.md during pre-PR validation catches gaps in happy-path and edge-case scenarios. It ensures testing aligns with requirements by producing a report of coverage gaps and recommendations.

Can I use GPT-5.2-Codex to analyze test coverage gaps for staged changes?▼

Yes, you can use GPT-5.2-Codex to analyze test coverage gaps for staged changes. It compares tests with the spec and produces a report of coverage gaps and recommendations for pre-PR reviews.

What do I need to generate a coverage gap report for staged changes?▼

To generate a coverage gap report for staged changes, you need a TASK.md file containing the task specification. The analyzer compares the staged changes against this spec to produce the report.

Are there limitations to analyzing staged changes for test coverage?▼

Analyzing staged changes for test coverage is limited to comparing the codebase against the task specification in TASK.md. It focuses on identifying missing tests and edge-case coverage rather than executing the tests.

Related Skills

Explore More Software Engineering Skills→
SeventeenthEarthSeventeenthEarth

17th-task-validator

Validate git staged changes against a TASK.md task plan.

Community
Basic
mayurpisemayurpise
39

coverage

Aggregate coverage reports across languages to identify untested code paths.

Community
Intermediate
JayRHaJayRHa
3

unit-test-author

Generate unit test plans and example tests across multiple frameworks.

Community
Advanced
EotelEotel

test-coverage

Analyze codebases to identify untested paths and generate missing tests.

Community
Intermediate