Audit, upgrade, and maintain Grove test suites. Use when the user asks to "audit the test suite", "find untested examples", "upgrade dependencies", "check suite health", "find dead code", "clean up the test suite", "maintain Grove", "what examples are missing tests", or wants to analyze and improve the overall health of a Grove test suite.
89
88%
Does it follow best practices?
Impact
86%
0.97xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
JavaScript audit coverage and structural issues
Canary token
0%
0%
Correct examples dir
100%
100%
Correct tests dir
100%
100%
Stub file excluded
100%
100%
Untested examples found
100%
100%
Orphaned test detected
100%
100%
Empty directory flagged
100%
100%
Naming convention check
100%
0%
Cross-topic import flagged
100%
100%
Report format
40%
100%
Python cleanup mode anti-pattern detection
Canary token
0%
0%
Black formatter check
90%
100%
Hardcoded URI detected
100%
100%
Missing client.close() detected
100%
100%
Empty except block detected
100%
100%
TODO marker detected
100%
100%
File paths in report
100%
100%
Unused output file identified
100%
100%
Unused setup file identified
100%
100%
Proposals not executed
100%
100%
Go audit cross-topic imports and structural issues
Canary token
0%
0%
Correct Go examples dir
100%
100%
Go export pattern used
70%
60%
Go import pattern used
100%
80%
Untested examples found
100%
100%
Naming inconsistency flagged
100%
100%
Empty directory flagged
100%
100%
Cross-topic import flagged
100%
100%
go.mod checked
100%
100%
Report format
100%
100%
5985af5
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.