- When finishing a task or request
review everything from the lens of code quality
Explore
128,564 skills indexed with the new KISS metadata standard.
review everything from the lens of code quality
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
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
while eslint.config.mjs still governs the repository's own JS/TS/Markdown/YAML linting.
but performant
focusing on compiler APIs