Discover blockchain code quality skills, compare source repositories and read the instructions for each workflow.
Use this agent when you have written or modified code and need a comprehensive review for quality, security, and maintainability. This agent should be used proactively after completing any coding task, whether...
Provides concise, focused code reviews matching exact task complexity requirements. Use when reviewing code quality, security, or when the user asks for code review.
Comprehensive code review using senior developer standards (YAGNI, DRY, avoiding god classes, data-driven architecture)
Code quality and CI requirements. Auto-triggered when discussing commits, PRs, or quality.
Review implementation fidelity against specifications by comparing actual code to spec requirements. Identifies deviations, assesses impact, and generates compliance reports for tasks, phases, or entire specs.
Code review workflow for evaluating changes against standards. Use when reviewing pull requests, commits, or diffs.
TypeScript/JavaScript standards for type-safe, maintainable code.
Clear writing standards based on Zinsser's principles. Use for documentation, commit messages, PR descriptions, and technical communication.
Comprehensive Convex code review checklist for production readiness. Use when auditing a Convex codebase before deployment, reviewing pull requests, or checking for security and performance issues in Convex fun...
Review code for quality, security, and best practices
Run full CI validation for the current project directory
リポジトリ全体を構造、コード品質、テスト、ドキュメントの観点から体系的にレビューし、優先度付きの改善レポートを生成する
RuffとMyPyを使用してコード品質をチェックする
This skill should be used when writing code, creating components, or implementing features. It provides the 23 essential coding standards that must be followed for every piece of code, ensuring scalable, effici...
Core development principles including anti-hallucination, anti-hardcoding, error handling, logging, testing, and security standards. Use during feature design, implementation, and code review to ensure code qua...
PREFERRED METHOD for Qodana scans. Always delegate to local-qodana-reviewer sub-agent when user mentions Qodana, code quality scan, static analysis locally, or requests to run Qodana. Do NOT run qodana commands...
Use when the user asks for a local CodeRabbit review before creating a pull request. Delegates to the specialized local-coderabbit-reviewer sub-agent to run the scan, analyze results, present a plan for fixes,...
This skill should be used when the user asks about "code quality", "formatting", "linting", "lint rules", "code style", "error handling", "unsafe code", "documentation comments", "doc comments", "rustfmt", "pre...
Self-review code changes before commit to ensure quality
Protects critical files and detects hardcoded secrets before risky edits. Use when "security check", "audit my settings", "check for secrets", before editing .zshrc or config files.
Verifies completed work against original specifications. Use when "verify spec", "check spec compliance", "verify against [spec file]", "spec verification for [implementation]".
Code quality checker skill. This skill should be used when the user wants to: (1) Run static analysis tools (mypy, pyright, ruff) on the codebase - triggered by "/check", "/check q", or "/check quality" (2) Fin...
Check and repair PyCharm/IntelliJ module configuration (.iml file). Triggered by "/cube-iml" or when user reports PyCharm doesn't recognize src/tests folders.
This skill should be used when the user asks to "clean up the code", "remove unnecessary comments", "simplify docstrings", "parameterize tests", or wants to review and clean up code.
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.