i18n-check
Analyze code for internationalization issues, understanding the UI context and user impact before flagging problems. Use when reviewing code for global readiness.
Analyze code for internationalization issues, understanding the UI context and user impact before flagging problems. Use when reviewing code for global readiness.
Prefer `cargo check` over `cargo build` when making Rust code changes. Use `cargo check` to quickly verify code compiles; only use `cargo build` when you need to run the executable.
Review code for quality, bugs, and best practices
Use when cleaning up AI-generated code on a branch - identifies and removes unnecessary comments, defensive checks, type casts, and style inconsistencies that don't match the codebase
Systematic code review checklist for quality, correctness, and maintainability
Must always be enabled when writing/reviewing TypeScript code.
Codex 后台审查流程。触发词:cha、审查、audit、codex、审计。支持后台批量审查模式,审查完成后汇总所有问题。
Validates filenames against repository CLAUDE.md standards. Detects violations including uppercase letters, spaces, special characters, missing versioning, and incorrect patterns. Use when you need to check if files follow naming conventions before organizing or committing.
Perform comprehensive code reviews with focus on correctness, performance, security, and maintainability. Use when reviewing pull requests, merge requests, or code changes.
Write structured code review comments using Conventional Comments format.
Generate a comprehensive code review prompt for the current branch that can be copied into another Claude session
Language-specific coding guidelines. Use when implementing code in Python or other supported languages.
Validate code quality and standards. Use when running linting, checking types, validating code style, or performing static analysis.
Go 代码注释规范检查与修复工具。自动化检查注释格式、术语一致性、包级别注释规范,利用大模型进行语义分析和注释生成,确保项目注释符合专业标准。
This skill should be used when writing code, creating components, or implementing features. It provides the 23 essential coding standards that must be followed for every piece of code, ensuring scalable, efficient, and maintainable codebases.
Reviews code for unnecessary complexity and suggests simplifications that make it easier for developers to understand
Audit code for WCAG 2.1 AA and EN 301 549 compliance. Checks keyboard navigation, ARIA usage, color contrast, forms, and media accessibility.
Validate and fix code by running tsc, linting, and tests sequentially.
Architecture analysis, violation detection, and pattern validation. USE WHEN: reviewing code architecture, identifying violations, verifying patterns, updating technical documentation. Reference: docs/02-architecture/ARCHITECTURE.md Examples: <example> Context: User wants to check if code follows architecture. user: "Analyze if the payment module follows our architecture" assistant: "I'll use architecture-analyzer to review against ARCHITECTURE.md." <commentary>Architectural review is architecture-analyzer specialty.</commentary> </example> <example> Context: Need to identify technical debt. user: "Find architectural violations in the services layer" assistant: "I'll use architecture-analyzer to scan for violations." <commentary>Violation detection is architecture-analyzer responsibility.</commentary> </example>
Execute code quality refactorings from gdscript-quality-checker reports. Use this when the user wants to implement the recommendations from a code review report.
Scan codebase for TODO, FIXME, and HACK comments and generate a prioritized report. Use when user wants to find or track technical debt.
inkLine code quality and simplification guidelines ensuring clear, consistent, maintainable code
**AUTO-ACTIVATE after code changes** (Write, Edit, NotebookEdit tools used). Comprehensive code review using 15-point checklist. Reviews: completeness, correctness, testability, reusability, consistency, design, error handling, security, documentation, performance, UX, data migration, dependencies. Triggers: code written, files modified, implementation complete, "review code"