verify-build
Verify the application builds successfully and check for type errors. Use when finished with changes, before committing, or when asked to check/verify work.
Découvrez les skills databases code quality, comparez leurs dépôts et consultez leurs instructions.
Verify the application builds successfully and check for type errors. Use when finished with changes, before committing, or when asked to check/verify work.
Ruffのlint/format実行と修正を扱う。AGENTS.mdに運用コマンドを追記するときに使う。
Builds and refactors code safely; prefers small diffs, clear validation steps, and testable outcomes.
Check if code is readable by non-developers - clear names, plain English comments, no jargon
Detects duplicate code and logic, suggesting abstractions, high-order functions, or strategy patterns.
next-intl audit for this repo (no hardcoded strings, locale routing correctness, messages parity). Triggers on "I18N:" prefix and i18n cleanup work.
Enforce TypeScript strict mode and type safety. Use when setting up projects, reviewing code, or when type errors are ignored. Covers strict flags, no-any rules, and type inference best practices.
Validate that input meets prerequisites based on the user's saved standards for the project type. Use at the start of any quality pipeline to ensure the user has provided sufficient requirements.
Guide for code conventions and formatting
Provides thorough code review guidance when users ask for code reviews, PR reviews, or feedback on their code. Activates when users mention reviewing code, checking for issues, or want feedback on implementatio...
Validate HTML5 structure and basic syntax. BLOCKING quality gate - stops pipeline if validation fails. Ensures deterministic output quality.
Senior frontend code review for Vue/TypeScript. Use when reviewing PRs, checking code quality, or validating against project conventions.
[slop] [debug] [unused] [duplicates] [all] - Cleans up code in the current branch. Removes AI artifacts, debug statements, unused code, and duplicates. Use when preparing for PR or cleaning up after AI-assisted...
Performs a comprehensive pre-merge review of changes on the current branch. Use when the user wants to verify their work before merging, check PR readiness, or run a final validation of tests, types, lint, and...
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.
Resolves build and compilation errors. Use when build fails or type errors occur.
Load coding conventions and style guidelines when writing or reviewing code. Ensures consistency with project standards.
Audits and validates skill definitions for quality, completeness, and best practices. Use when reviewing existing skills for proper formatting, evaluating if skills should be split into sub-skills, or ensuring...
Systematic code review following BUGBOT patterns and quality standards
Review staged and unstaged changes for pydantic-ai coding convention violations using a fresh subagent
Enforce colon-based single-line file references (path:line) with no ranges; use whenever providing file paths with line context or normalizing user-supplied references.
Complete code review workflow for both requesting and receiving reviews. Use when creating PRs, reviewing code, or responding to feedback.
Analyzes modules for Single Responsibility Principle violations and proposes splitting plans (Service, Repository, Utils, Controller).
This skill should be used when the user asks to "review code", "review this PR", "code review", "audit this code", or mentions reviewing pull requests, security checks, or code quality. Covers security (OWASP),...
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é.