- **Analysis:** Use `read_file`
`grep_search`
Explore
116,689 skills indexed with the new KISS metadata standard.
`grep_search`
thats fine. Just do as much as you can
precise generics
supported patterns and best practices; propose migrations when older or deprecated approaches are encountered.
checking for type errors
include error handling
you should redirect the command to a file and read it using proper tools. Put these files in the `temp/` directory. This folder is automatically cleared between prompts
fail gracefully. Do not crash the linter process.
testable utility functions.
keep that authored metadata static and explicit.
check whether the standard library
docs
scope it carefully and document the expected `customSyntax` or file context.
comments
report only.
`messages`
and use installed utility-type libraries only when they clearly improve intent and match repository conventions.
repeated reparsing of selector/value strings
`walkRules`
coverage outputs
peer dependency ranges
prefer the repo's contributor scripts over hand-editing generated sections.
think beyond only unit tests.
many plugin repos also enforce: