Total 50,341 skills, Code Quality has 2286 skills
Showing 12 of 2286 skills
Review code changes in a feature branch before merging. Use when asked to review a branch, review changes, check a PR, or audit code before merge. Compares the current branch against the default branch (main/master) and categorizes issues by severity (Critical, Major, Minor) with actionable solutions.
Performs comprehensive PR code review from 5 perspectives (quality/performance/tests/docs/security) in parallel, providing Blockers/Suggestions/Nice-to-have and merge decision. Args: /review [owner/repo] [pr-number] [--focus all|security|perf|qa|docs|types] Activates when user mentions "review", "PR確認", "コードレビュー", "マージ判定".
Detect and refactor code duplication with PMD CPD. TRIGGERS - code clones, DRY violations, duplicate code.
Function design patterns emphasizing single responsibility and clarity.
Dynamically validate that the implemented codebase matches architectural decisions documented in plan files. Use when validating implementation matches planning documents, checking for architecture drift, or preparing for architecture reviews.
Comprehensive code review workflow - parallel specialized reviews → synthesis
Run a full-scale implementation review with parallel subagents for plan alignment, UI verification, technical and strategic analysis, and test coverage gap closure across app and database layers.
Structures the human review experience for factory-mode builds. Audit trail summaries, PR digests, retrospective synthesis, quality trend tracking, and autonomy tuning interface. Activate during Phase 3 human review.
Methodology for debugging non-trivial problems systematically. This skill should be used automatically when investigating bugs, test failures, or unexpected behavior that isn't immediately obvious. Emphasizes hypothesis formation, parallel investigation with subagents, and avoiding common anti-patterns like jumping to conclusions or weakening tests.
Applies a modified Fagan Inspection methodology to systematically resolve persistent bugs and complex issues. Use when multiple previous fix attempts have failed repeatedly, when dealing with intricate system interactions, or when a methodical root cause analysis is needed. Do not use for simple troubleshooting. Triggers after multiple failed debugging attempts on the same complex issue.
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>
Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.