coding-standards
コードの品質問題、アンチパターン、可読性を検査。機能実装、コードレビュー、リファクタリング時に使用。
Discover databases code quality skills, compare source repositories and read the instructions for each workflow.
コードの品質問題、アンチパターン、可読性を検査。機能実装、コードレビュー、リファクタリング時に使用。
Review code quality, security, and maintainability before committing. Use when reviewing code changes, checking code quality, performing security review, or validating changes before commit.
Conduct context-driven code reviews focusing on quality, testability, and maintainability. Use when reviewing code, providing feedback, or establishing review practices.
Reviews code for quality, security, performance, and accessibility issues. Use when user mentions reviews, code review, security, performance, quality checks, PRs, diffs, or change review. Do NOT load for: impl...
Systematic methodology to reduce skill file size through externalization, consolidation, and progressive loading patterns. Triggers: large skill, skill optimization, skill size, 300 lines, inline code, skill r...
Detect codebase bloat through progressive analysis: dead code, duplication, complexity, documentation bloat. Triggers: bloat detection, dead code, code cleanup, duplication, technical debt, unused code Use wh...
Configure comprehensive three-layer pre-commit quality system with linting, type checking, and testing enforcement
Audit shell scripts for correctness, portability, and common pitfalls. Triggers: shell script, bash, sh, script review, pipeline, exit code Use when: reviewing shell scripts, CI scripts, hook scripts, wrapper...
Adds the standard open-source license header to new source files. Use involves creating new code files that require copyright attribution.
Create high-quality Pull Requests with conventional commits and proper descriptions. Trigger: When creating PRs, writing PR descriptions, or using gh CLI for pull requests.
TRIGGERS: "do I need tests?", "test coverage check", "ready to merge", "pre-merge review", test verification, coverage check, missing tests, test strategy. USE WHEN: Code is ready to merge and needs test covera...
TRIGGERS: "code quality check", "is this clean enough?", "ready for review", code quality verification, naming check, DRY check, structure review. USE WHEN: Code is ready for review and needs quality verificati...
TRIGGERS: "review my code", "is this clean?", "code review", "refactor this", "code quality", "refactoring", "cleaning up", "organizing", "structuring code", "naming this", "splitting function", "extract method...
Development tools, linting, and testing for JavaScript projects.
Standards for analysis, linting, formatting, and automation.
Environment variables validation and ConfigModule setup.
Review a CodeRabbit PR comment and produce an action plan when prompted to analyze a review comment.
Use when reviewing pull requests with comprehensive code analysis, incremental or full review options, and constructive feedback - provides thorough code reviews with severity ratings
Use when creating or updating pull requests with comprehensive descriptions and meaningful commits - streamlines PR workflow with branch management and commit best practices
Python 开发规范,包含 PEP 8 风格、类型注解、异常处理、测试规范等
Check .meta.yml and snapshot .dvc files for spelling typos using codespell. Use when user mentions typos, spelling errors, metadata quality, or wants to check metadata files for mistakes.
Code refactoring expert for improving code quality, readability, maintainability, and performance. Specializes in Java and Python refactoring patterns, eliminating code smells, and applying clean code principle...
Comprehensive code reviewer for Java and Python implementations focusing on correctness, efficiency, code quality, and algorithmic optimization. Reviews LeetCode solutions, data structures, and algorithm implem...
Review Clojure and ClojureScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing Clojure/ClojureScript...
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.