- Sometimes you may need to take other steps that aren't explicitly requests (running tests
checking for type errors
Explore
129,324 skills indexed with the new KISS metadata standard.
checking for type errors
maintainability
review everything from the lens of code quality
fail gracefully. Do not crash the linter process.
testable utility functions.
docs
keep that authored metadata static and explicit.
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.
`messages`
repeated reparsing of selector/value strings
`walkRules`
coverage outputs
prefer the repo's contributor scripts over hand-editing generated sections.
peer dependency ranges
think beyond only unit tests.
many plugin repos also enforce:
sync/validation flows may include:
configs
that often includes:
entrypoints