docs(skills): minimal test coverage rule in testing-patterns - #3094
Merged
Conversation
New code earns a test only when nothing already goes red on the same breakage (another test, or mypy over library code). No docstrings on tests beyond the regression pattern's issue-URL; explain with a single-line comment over the line instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
IvanKirpichnikov
approved these changes
Sep 4, 2026
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a rule to the
testing-patternsskill: new code earns a test only when nothing else already goes red on the same breakage (another test, ormypyover library code that already exercises the path). Also tightens the docstring policy — tests carry no docstring beyond the regression pattern's issue-URL; explain with a single-line comment over the line instead of prose in a docstring.This absorbs two standing pieces of maintainer feedback (fewer, essential tests; no test docstrings) into the checked-in skill instead of leaving them as ephemeral guidance.
Type of change
Checklist