code-review-skill
言語共通のコードレビュースキル。コメント最適化、マジックナンバー検出、構造改善のレビューを実施。コードレビュー、PRレビュー、コード品質チェックを依頼された際に使用。
言語共通のコードレビュースキル。コメント最適化、マジックナンバー検出、構造改善のレビューを実施。コードレビュー、PRレビュー、コード品質チェックを依頼された際に使用。
Apply kinemotion development standards. Use when writing Python code, creating tests, modifying the kinemotion codebase, or reviewing code quality.
Code review checklist and guidelines. Use when reviewing code, creating review comments, or preparing code for review.
Parse and validate project specifications. Use when loading YAML/JSON specs, validating spec structure, extracting requirements, or converting between spec formats.
Validates type consistency across Rust, TypeScript, PostgreSQL boundaries. Use when reviewing code, debugging type mismatches, or validating API contracts. Triggers on: check consistency, validate types, find mismatches, cross-language.
Revisa código en documentos LaTeX para asegurar convenciones de nombrado. Usa cuando el usuario mencione revisar código, verificar nombres de variables/funciones, o validar estilo de código en documentos.
TypeScript coding standards. Use when: writing or reviewing TypeScript code (*.ts, *.tsx).
Runs frontend quality checks including TypeScript, ESLint, and tests. Use before commits, PRs, or when the user says "check frontend", "run frontend tests", "lint frontend".
Code metrics calculation methodology for static analysis
Validate code before committing - runs linting, formatting, and tests. Use when preparing to commit, before git add, or when checking if code is ready to push.
Self-review loop for code changes. Use when Codex edits files or prepares a PR and should run `codex exec --sandbox workspace-write review --base BASE`, fix findings, and re-run until clean (max 10). Also run tests when a test command is configured or detectable.
Use when reviewing code for Architecture Decision Record (ADR) compliance during refactoring or code review - checks code against all project ADRs and reports violations with specific fixes
Implement code quality ratchets to prevent proliferation of deprecated patterns. Use when (1) migrating away from legacy code patterns, (2) enforcing gradual codebase improvements, (3) preventing copy-paste proliferation of deprecated practices, or (4) setting up pre-commit hooks to count and limit specific code patterns. A ratchet fails if pattern count exceeds OR falls below expected—ensuring patterns never increase and prompting updates when they decrease.
Perform code review for PhotoClove codebase. Automatically invoked when reviewing code changes, PRs, or when asked to check code quality. Uses project-specific guidelines and knows what NOT to flag.
Review layout consistency (spacing, alignment, grid usage). Use to ensure visual consistency across components.
Generate .vscode/settings.json configuration.
Use when completing implementation, before escalating to human review, or when human checkpoint is reached - performs AI-assisted code review covering security, AI-specific issues, logic errors, and architecture to ensure humans see fresh analysis
Use at the start of a Codex session (especially sandboxed) to run `scripts/codex-sandbox-preflight.sh` and interpret network + writable_roots constraints.
Fixes naming convention issues including unused variables, single-letter names, and non-standard abbreviations. Use when encountering no-unused-vars errors or reviewing variable naming.