Check and enforce project policies from CLAUDE.md and POLICIES.md. Use when validating implementations against project standards, checking code style requirements, or ensuring compliance with development guidelines.
Review code for quality, security vulnerabilities, and best practices compliance
Rust coding standards (Japanese comments required, error handling, logging, naming conventions). Use when writing new code, adding error handling, logging, fixing errors, asking about coding style, thiserror, tracing, naming conventions, or code review.
Unified linting scripts for all services in the monorepo. Use when the user wants to lint code, check formatting, or run type checks.
実装完了後のテスト、lint、ベストプラクティスレビューを自動実行するスキル。 以下の状況で使用: (1) ユーザーが「実装完了」「完了」「できた」「終わった」「実装した」「書き終わった」などと発言した時 (2) ユーザーが明示的に「/post-impl-validator」を実行した時 (3) ファイル編集後に「コミットして」「PRを作成」「プッシュして」「push」などと依頼された時 (4) ユーザーが「テストを実行して」「テストして」「lintを確認して」「lintかけて」と個別に依頼した時 (5) ユーザーが「レビューして」「チェックして」「検証して」と品質確認を求めた時 (6) ユーザーが「これで問題ない?」「大丈夫?」と確認を求めた時
Validate links and references in SKILL.md files using deterministic scripts
Production-ready code implementation following approved designs. Writes clean, tested, documented code. Zero linting violations. All code includes tests.
PRの全フィードバック（CodeQL、Copilotレビュー、手動コメント）を取得し、漏れなく対応する
コード品質チェック専門スキル。TypeScript/JavaScript ファイルの ESLint、型チェック、コーディング規約を検証する。
Systematic code review checklist for quality and security
PR 코드 리뷰, 개선 제안, 자동 머지 에이전트. 코드 품질, 테스트, 보안 검사 통합.
Verify the junior can explain and defend every line of code they wrote. This gate BLOCKS completion if failed.
Use these when you want low-noise lint/test output (good for LLM/CI logs) while staying aligned with repo policy.
Use this agent when you need to review Rails code changes with an extremely high quality bar. This agent should be invoked after implementing features, modifying existing code, or creating new Rails components. The agent applies Kieran's strict Rails conventions and taste preferences to ensure code meets exceptional standards.\n\nExamples:\n- <example>\n Context: The user has just implemented a new controller action with turbo streams.\n user: "I've added a new update action to the posts controller"\n assistant: "I've implemented the update action. Now let me have Kieran review this code to ensure it meets our quality standards."\n <commentary>\n Since new controller code was written, use the kieran-rails-reviewer agent to apply Kieran's strict Rails conventions and quality checks.\n </commentary>\n</example>\n- <example>\n Context: The user has refactored an existing service object.\n user: "Please refactor the EmailProcessor service to handle attachments"\n assistant: "I've refactored the EmailProc
Automatically detect and fix TypeScript unused imports/variables errors (TS6133). Use when encountering "declared but its value is never read" errors during tsc, build, or CI checks.
Simplicity-focused code review. Checks for over-engineering, unnecessary abstraction, and premature optimization.
Validate that orchestrator plan files conform to expected JSON schema. Use before workers read plan files or after orchestrators create them to ensure proper structure and required fields.
Linter-driven refactoring patterns to reduce complexity and improve code quality. Use when linter fails with complexity issues (cyclomatic, cognitive, maintainability) or when code feels hard to read/maintain. Applies storifying, type extraction, and function extraction patterns.
Formatting rules for TypeScript conditional types. Use when writing complex conditional types to ensure debuggable, maintainable formatting with proper alignment.
Architecture and code review guidance for this repo, with RSC boundaries, SOLID, quality gates, and mentoring. Use when reviewing changes or advising design.
