reclassify-tests

Mark tests not demonstrated in checkpoint specs with pytest functionality marks.

138|30|Updated Dec 17, 2025

Search Tags:#testing #pytest #test-coverage #spec-analysis #marker #reclassification

Ready to run

npx skills add https://github.com/SprocketLab/slop-code-bench --skill reclassify-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reclassify-tests
Source: https://github.com/SprocketLab/slop-code-bench/tree/main/.claude/skills/reclassify-tests
Command: npx skills add https://github.com/SprocketLab/slop-code-bench --skill reclassify-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies tests whose behavior is not explicitly demonstrated in the checkpoint spec and marks them as functionality using pytest marks to clarify core versus extended coverage.

Core Features & Use Cases

Analyze a problem's checkpoint spec and its tests to identify implicit behaviors not shown in examples.
Mark non-explicit tests with @pytest.mark.functionality to separate core demonstration from inferred behavior.
Generate a reclassification report detailing decisions, rationale, and any test modifications for review.

Quick Start

Invoke /reclassify-tests <problem> <checkpoint> to classify tests based on spec coverage.

Frequently Asked Questions about reclassify-tests

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

FAQPage Schema

How do I separate core spec tests from inferred functionality tests in pytest?▼

You can separate core spec tests from inferred functionality tests by analyzing checkpoint spec examples against your test files and marking non-explicit behaviors with @pytest.mark.functionality. This clarifies which tests demonstrate core requirements versus extended coverage.

What is test reclassification by spec coverage?▼

Test reclassification by spec coverage is the process of identifying tests whose behavior is not explicitly demonstrated in the checkpoint spec and tagging them as functionality. It distinguishes core demonstration from inferred behavior to clarify test suite scope.

How do I mark implicit test behaviors as functionality using pytest marks?▼

To mark implicit test behaviors as functionality using pytest marks, analyze your spec examples and test files to find behaviors not explicitly shown, then apply @pytest.mark.functionality to those tests and generate a reclassification report detailing the decisions.

Can I analyze pytest fixtures to determine core versus functionality coverage across checkpoints?▼

Yes, you can analyze pytest fixtures alongside spec examples and test files to determine core versus functionality coverage across checkpoints. The analysis identifies which tests demonstrate explicit spec behavior and which test inferred functionality.

Why are some pytest tests not explicitly demonstrated in the checkpoint spec?▼

Some pytest tests are not explicitly demonstrated in the checkpoint spec because they verify inferred or extended behaviors beyond the core examples. Reclassification identifies these tests and marks them as functionality to separate core demonstrations from implicit coverage.

Does test reclassification modify existing test files or only generate a report?▼

Test reclassification both generates a reclassification report detailing decisions and rationale, and outputs any test modifications needed for review. This includes applying pytest marks to classify tests based on spec coverage analysis.