codereview-style
Review code style, maintainability, and documentation. Checks readability, naming, modularity, abstractions, and documentation accuracy. Use as a final pass on all files.
Discover blockchain code quality skills, compare source repositories and read the instructions for each workflow.
Review code style, maintainability, and documentation. Checks readability, naming, modularity, abstractions, and documentation accuracy. Use as a final pass on all files.
Development process rules for this project including testing, branching, and commit standards. Use when implementing features, fixing bugs, or making any code changes.
Code quality evaluation criteria for reviews. Use when reviewing code design, architecture, maintainability, or identifying potential issues.
Performs comprehensive code review of a GitHub PR. Use when: user wants to review a PR, check code changes, or analyze pull request.
Performs thorough code review with focus on correctness, security, performance, and maintainability. Provides actionable feedback with specific line references.
Use when writing tests - test structure, mocking patterns, pre-commit checks
Master type safety patterns - fix type errors at source, never use type: ignore or any, prefer Pydantic models, use type stubs for external libraries
Pedantic backend pre-commit + atomic-commit skill for Django/Optimo repos that enforces local repo rules, pre-commit hooks, and security helpers (no AI signatures in commit messages).
Generate weekly code-review digest docs from PR review comments for any GitHub repo, capturing themes, repeated issues, and concrete takeaways.
Hyper-pedantic Django code review skill emulating Monty's correctness-first, multi-tenant-safe review style.
Refactor Django/Python code to improve maintainability, readability, and adherence to best practices. Transforms fat views, N+1 queries, and outdated patterns into clean, modern Django code. Applies Python 3.12...
License checking and compatibility. Use when evaluating dependency licenses.
Standards for writing clear, concise git commit messages. Use when creating commits, reviewing commit history, or establishing git workflow conventions.
Strict TypeScript configuration with all safety flags enabled. Use when initializing TypeScript projects or enforcing type safety.
Mandatory verification protocol after code changes for JavaScript/TypeScript projects. Use after any code modification to ensure quality.
ESLint 9.x flat configuration patterns. Use when setting up ESLint with TypeScript.
Standards for maintaining high code quality including comments, test coverage, and documentation practices
Pre-commit hook setup with Husky and lint-staged. Use when configuring git hooks.
Code quality standards, linting rules, and best practices for clean Solidity code. Use when reviewing code quality or establishing project standards.
Biome linter/formatter setup. Use when configuring Biome as an alternative to ESLint + Prettier.
Creates and manages Biome GritQL custom lint rules to enforce coding patterns. Use when creating linter rules, enforcing code conventions, preventing anti-patterns, or when the user mentions Biome, GritQL, cust...
Testing patterns with Bun test runner, coverage thresholds, mocking, and CI/CD integration. Use when writing tests, organizing test files, or setting up quality gates.
Fix go vet warnings
Fix staticcheck issues
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.