hf.check-test-counterpart

This Skill nudges you to add Python tests by checking newly created Python source files for missing test counterparts. It prints a non-blocking reminder during code creation without halting your development progress.

No, the missing test reminder is strictly non-blocking and only prints a prompt when a test counterpart is absent. It validates file types and ignores existing tests, allowing code creation to proceed without interruption.

The check ignores __init__.py files, migration files, and non-Python paths. It validates new Python source files and skips existing tests to accurately detect when a test counterpart is missing.

The nudge detects existing tests by validating typical Python project layouts, specifically checking for a tests/ directory and the test_*.py file naming pattern. It skips these paths so only missing counterparts trigger the reminder.

Yes, you can use this reminder during early Python development because it operates during code creation to catch missing tests. It validates new files on the fly and prints a nudge if no test counterpart exists.

The best way to maintain test coverage without blocking progress is using a non-blocking nudge that validates new Python files for missing test counterparts. It prints a reminder without interrupting code creation.