test-coverage
Analyze test coverage, identify gaps, and recommend test improvements. Use when relevant to the task.
Discover blockchain code quality skills, compare source repositories and read the instructions for each workflow.
Analyze test coverage, identify gaps, and recommend test improvements. Use when relevant to the task.
Detect orphaned tests, obsolete assertions, and test-code misalignment. Use for test suite maintenance, cleanup, and traceability validation. Use when relevant to the task.
Check code style compliance. Use when asked to validate code style, check naming conventions, review comments quality, or ensure file naming follows conventions. Works on whole codebase or specific changes (bra...
Validate code for KISS and DRY principles. Use when asked to check for simplification opportunities, reduce duplication, review code complexity, or ensure maintainability. Works on whole codebase or specific ch...
Run full validation to ensure code is ready for merge. Use before merging PRs, when asked to validate readiness, or as a final check before requesting review.
Review code changes for quality, correctness, and best practices. Use when asked to review a PR, review changes, or assess code quality before merge.
Installs Sanity agent rules directly into the local project. Use when setting up a new editor environment.
Configures Sanity Visual Editing for your front-end framework. Use when setting up live preview or click-to-edit overlays.
Review frontend code for best practices, bugs, and improvements. Use when reviewing PRs, checking code quality, or before committing.
Review Python code for bugs, security issues, and best practices
Standards for self-documenting code and minimal comments. Use when auditing inline documentation or deciding when comments add value vs clutter.
Code review guidelines and checklist. Use when reviewing PRs or preparing code for review.
Configure markdownlint rules and options including rule management, configuration files, inline comments, and style inheritance.
Use when applying Biome's linting capabilities, rule categories, and code quality enforcement to JavaScript/TypeScript projects.
Use automatically during development workflows when making claims about tests, builds, verification, or code quality requiring concrete evidence to ensure trust through transparency.
Use when configuring Clippy for Rust projects with TOML config, lint groups, attributes, and workspace setup.
Use when eSLint built-in rules including rule configuration, severity levels, and disabling strategies.
Use when creating custom Credo checks for project-specific code quality rules and standards in Elixir.
Use when configuring Dialyzer for Erlang/Elixir type checking and static analysis.
Use when configuring shfmt for shell script formatting including .shfmt.toml setup, EditorConfig integration, and project-specific settings.
Use during verification phase when conducting thorough code reviews and providing constructive feedback based on universal software quality principles.
Use when modifying existing files, refactoring, improving code quality, or touching legacy code by applying the Boy Scout Rule to leave code better than you found it.
Use when understanding and fixing common Credo check issues for Elixir code quality and consistency.
Integrate markdownlint into development workflows including CLI usage, programmatic API, CI/CD pipelines, and editor integration.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.