lang-rust
Rust conventions and reliability checklist for agents using cargo, clippy, and tests.
Découvrez les skills blockchain code quality, comparez leurs dépôts et consultez leurs instructions.
Rust conventions and reliability checklist for agents using cargo, clippy, and tests.
This skill should be used when the user needs help "fixing markdown issues", "repairing markdown lint errors", "resolving markdownlint violations", "MD001", "MD022", "MD024", "MD031", "MD042", "lint error", or...
Code quality enforcement with ESLint static analysis, VSCode workspace management, and automated code fixes. Supports JavaScript, TypeScript, React, Node.js with security and performance linting rules.
Handle code review feedback with technical rigor. Use this skill when receiving code review comments or feedback. Verify before implementing, ask before assuming, prioritize technical correctness over performat...
Automatic quality control, linting, and static analysis procedures. Use after every code modification to ensure syntax correctness and project standards. Triggers onKeywords: lint, format, check, validate, type...
Core coding standards, SOLID principles, Clean Code, and naming conventions. Use this skill for any coding task to ensure consistency.
Build quality standards, validation checkpoints, and compilation requirements
Comprehensive Python coding standards and style conventions for maintaining consistent, high-quality code across uv-managed Python projects
Guide for reviewing code quality, identifying issues, and suggesting improvements. Use when asked to review code, check for best practices, or conduct code reviews.
Code comment style guidelines - when to comment and when not to
Perform systematic self-review of code changes before commits using structured checklist. Validates architecture boundaries, code quality, test coverage, documentation, and project-specific anti-patterns. Use b...
Validate and optimize CLAUDE.md files using Anthropic's best practices for focused sessions. Detects contradictions, redundancy, excessive length (200+ lines), emphasis overuse (2%+ density), broken links, and...
Use this skill when writing, editing, or reviewing Python code. Ensures code follows PEP 8 standards and Python best practices.
Review code for correctness, design quality, and complexity using principles from "A Philosophy of Software Design." Use this skill when reviewing pull requests, code changes, diffs, or when asked to find bugs,...
Validates that all imports follow fail-fast principle by detecting try/except ImportError patterns, conditional imports, and optional dependencies. Use before commits, when modifying imports, during code review...
Perform concise, high-quality code reviews focused on hygiene, simplicity, maintainability, documentation, correctness, performance, security, and robustness. Use when reviewing PRs/diffs/files to surface risks...
Safe-by-default git workflow and Conventional Commits. Triggers on git operations, reviewing diffs, staging files, creating commits, or branch changes. Prevents destructive operations without consent.
Senior developer code review skill. Use when reviewing code for quality, security, performance, and best practices. Triggers on code changes, PR reviews, or explicit review requests.
執行全面性的程式碼審查,提供具建設性、可落地執行的回饋,涵蓋安全性、效能、程式碼品質、架構設計與測試等面向。
Review implementation quality and regression risks via claude-delegator (Code Reviewer expert). Use after implementation for complex tasks, refactors, or API changes.
Run dual type checking with pyright (fast, development) and mypy (thorough, CI/CD). Use when checking types, before commits, debugging type errors, or validating type annotations. Explains why both tools requir...
CLI review and testing checklist
Review uncommitted code changes against project standards. Similar to /review-code but scoped to changed files only. Suggests fixes and in auto-edit mode fixes automatically.
Logic validation by verbalization. Translate code to plain English to catch semantic errors. Use before running complex logic or when debugging "it should work" failures.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.