Repository navigation
Focus testing skill on observable runtime behavior - #1
Merged
Merged
Conversation
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
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.
Summary
Why
The previous wording organized testing around proof and included static checks in the recommended workflow. That made the skill less direct about its main job: exercising behavior that a real caller can observe.
Static checks now appear only as a narrow caution because they are brittle and difficult to maintain; they are marked as extremely discouraged without making that point the skill's main theme.
Impact
Agents invoking
$testingwill prioritize runtime behavior, meaningful risks, and maintainable tests. The UI prompt and repository descriptions now present the same focus.Validation
quick_validate.py skills/testingvalidatedevenv test