GitHub
ownership-gate
Verify the junior can explain and defend every line of code they wrote. This gate BLOCKS completion if failed.
☆ 124Voir le skill
Skills IA tools code quality
Découvrez les skills tools code quality, comparez leurs dépôts et consultez leurs instructions.
Catégories: tools code quality
tools code quality Effacer les filtres
Explorer
GitHub
database-fundamentals
Auto-invoke when reviewing schema design, database queries, ORM usage, or migrations. Enforces normalization, indexing awareness, query optimization, and migration safety.
☆ 124Voir le skill
GitHub
test-coverage-analyzer
Analyzes test coverage gaps and suggests test cases for untested code paths. Use when user requests test improvements, coverage analysis, or wants to increase test coverage.
☆ 124Voir le skill
GitHub
global-commenting
Write minimal, evergreen code comments that explain complex logic without documenting obvious behavior or temporary changes. Use this skill when adding comments to PHP files, TypeScript/JavaScript files, or any...
☆ 124Voir le skill
GitHub
line-limit
Enforce file line count limits (200 recommended, 300 max) for CODE IMPLEMENTATION files only. Use this when reviewing code, creating files, or when files exceed line limits and need modularization.
☆ 124Voir le skill
GitHub
typescript-strict
Strict TypeScript rules. Use when writing ANY TypeScript.
☆ 124Voir le skill
GitHub
clean-code-reviewer
Analyze code quality based on "Clean Code" principles. Identify naming, function size, duplication, over-engineering, and magic number issues with severity ratings and refactoring suggestions. Use when the user...
☆ 124Voir le skill
GitHub
configuration-validator
Validates environment variables, config files, and ensures all required settings are documented. Use when working with .env files, configs, or deployment settings.
☆ 124Voir le skill
GitHub
test-driven-development
Enforce RED-GREEN-REFACTOR cycle. Use when implementing features, fixing bugs, or writing any production code.
☆ 124Voir le skill
GitHub
file-name-wizard
Audit all filename and naming conventions in the codebase against CLAUDE.md standards and common patterns. Use when user asks to check naming conventions, audit filenames, find naming inconsistencies, or valida...
☆ 124Voir le skill
GitHub
refactor-assistant
Automated code refactoring suggestions and implementation.
☆ 124Voir le skill
GitHub
testing-fundamentals
Auto-invoke when reviewing test files or discussing testing strategy. Enforces testing pyramid, strategic coverage, and stack-appropriate frameworks.
☆ 124Voir le skill
GitHub
standards-extraction
Extract coding standards and conventions from CONTRIBUTING.md, .editorconfig, linter configs. Use for onboarding and ensuring consistent contributions.
☆ 124Voir le skill
GitHub
global-coding-style
Write clean, consistent code following naming conventions, DRY principles, small focused functions, automated formatting, and meaningful variable names. Use this skill when writing or refactoring any code in an...
☆ 124Voir le skill
GitHub
no-hardcoding
Forbid hardcoded values in code. Use this when reviewing code, writing new features, or when magic numbers/strings are detected. Enforces constants, env variables, and config files.
☆ 124Voir le skill
GitHub
html-structure-validate
Validate HTML5 structure and basic syntax. BLOCKING quality gate - stops pipeline if validation fails. Ensures deterministic output quality.
☆ 124Voir le skill
GitHub
code-reviewer
Use when asked to review MERN stack code - comprehensive code reviewer that checks project health, security, maintainability, performance, testing, and architecture. Combines general code quality analysis with...
☆ 124Voir le skill
GitHub
code-analysis
Check if code is readable by non-developers - clear names, plain English comments, no jargon
☆ 124Voir le skill
GitHub
code-review
This skill should be used when the user requests a code review of changed files. Use this to review git-diffed files for security vulnerabilities (OWASP Top 10), performance issues (O(N) complexity, ORM optimiz...
☆ 124Voir le skill
GitHub
verification-before-completion
Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.
☆ 124Voir le skill
GitHub
security-fundamentals
Auto-invoke when reviewing authentication, authorization, input handling, data exposure, or any user-facing code. Enforces OWASP top 10 awareness and security-first thinking.
☆ 124Voir le skill
GitHub
quality-fixer
Automatically apply safe quality fixes including formatting (Black, isort), linting (Ruff auto-fixes), and resolve formatter conflicts. Use when quality checks fail or before committing code.
☆ 124Voir le skill
GitHub
quality-gates
Run comprehensive quality checks including linting, type checking, tests, and security audits before commits or deployments
☆ 124Voir le skill
GitHub
lint
How to lint and typecheck in this project. Load when implementing or verifying code.
☆ 124Voir le skill
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é.