code-review
Padrões e checklist para code review
Découvrez les skills content media code quality, comparez leurs dépôts et consultez leurs instructions.
Padrões e checklist para code review
Perform code review: detect risks, style issues, error handling gaps (report-only).
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.
Automated review rules for opal-frontend-common-ui-lib PRs. Use when asked to review code, run @codex review, or provide PR feedback; apply severity levels and the required comment format.
Python best practices e styleguide
This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framew...
Rust coding style and decision defaults for API design, errors, structure, naming, ownership, async boundaries, performance tools, and testing choices. Use when writing or reviewing Rust code and when choosing...
Identifies anti-patterns specific to amplihack philosophy. Use when reviewing code for quality issues or refactoring. Detects: over-abstraction, complex inheritance, large functions (>50 lines), tight coupling,...
Security guidelines for frontend code. Covers token storage, XSS prevention, authorization, and secure coding practices. CRITICAL INSTRUCTION You MUST ALWAYS use this skill before editing/writing any file match...
PRのコードを静的レビューし、結果をローカルファイルに出力する。Usage: /review [PR_NUMBER]
Contains rules that MUST ALWAYS be applied to EVERY TypeScript file. Covers method definitions, constants, imports, and type safety. CRITICAL INSTRUCTION You MUST ALWAYS use this skill before editing/writing an...
Building a positive code review culture that catches bugs, shares knowledge, maintains code quality, and builds team trust through effective review practices.
Philosophy-aware PR reviews checking alignment with amplihack principles. Use when reviewing PRs to ensure ruthless simplicity, modular design, and zero-BS implementation. Suggests simplifications, identifies o...
Run linters and fix violations, formatting errors, or style mismatches using Trunk. Use when code quality checks fail, before submitting PRs, or to repair "broken" linting states.
Run unit tests and automatically fix code failures, regression bugs, or test mismatches. Use when tests are failing, after implementing new features, or to repair "broken" tests.
Policy สำหรับ enforce code quality ผ่าน linting, testing, และ type checking ใน CI pipeline
Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation
Format code according to project standards. Use after making changes or before committing.
Validate .meaning/index.yaml for errors and warnings
Verifies code follows Clean Architecture principles in Polibase. Activates when creating or modifying src/domain, src/application, src/infrastructure, or src/interfaces files. Checks dependency rules, entity in...
Criteria for reviewing Codex worker outputs across 5 dimensions. Use when reviewing code submitted by workers before approval.
Review implementation quality and regression risks via claude-delegator (Code Reviewer expert). Use after implementation for complex tasks, refactors, or API changes.
Validate integration impact and regression risks via claude-delegator (Code Reviewer expert). Use for complex tasks or API integration.
Genera mensajes de commit descriptivos siguiendo Conventional Commits. Analiza cambios y sugiere mensajes claros. Úsalo cuando escribas commits o menciones "commit".
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é.