- Sometimes you may need to take other steps that aren't explicitly requests (running tests
checking for type errors
Explore
124,702 skills indexed with the new KISS metadata standard.
checking for type errors
supported patterns and best practices; propose migrations when older or deprecated approaches are encountered.
maintainability
fail gracefully. Do not crash the linter process.
review everything from the lens of code quality
testable utility functions.
scope it carefully and document the expected `customSyntax` or file context.
check whether the standard library
comments
report only.
and use installed utility-type libraries only when they clearly improve intent and match repository conventions.
`walkRules`
repeated reparsing of selector/value strings
peer dependency ranges
coverage outputs
sync/validation flows may include:
think beyond only unit tests.
many plugin repos also enforce:
that often includes:
entrypoints
existing repository helpers
check whether there is already a matching script
Quality Gates
hard truth. If I propose a rule that is impossible to implement performantly