dfcode-review
Core code review logic. Trigger when invoked by review commands. Do not trigger directly from user requests - use /df:review or /df:azdo:review instead.
Core code review logic. Trigger when invoked by review commands. Do not trigger directly from user requests - use /df:review or /df:azdo:review instead.
Run static analysis (linting, type checking) on the codebase.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable
Validate skills and plugins with deterministic evidence bundles and strict schema gates. Use when auditing changes or enforcing compliance. Trigger with 'run validation' or 'audit validators'.
Create validation logic for F# backends with error accumulation and async validation. Use when: "add validation", "validate X", "input validation", "complex validation", "business rules", "check email", "required fields", "async validation", "database uniqueness", "cross-field validation", "validation errors". Creates validators in src/Server/Validation.fs. Use for complex scenarios; basic validation patterns are in fsharp-backend skill.
Audit code for over-engineering, premature optimization, and cognitive complexity. Identifies unnecessary abstractions, YAGNI violations, and overly complex solutions. Read-only analysis. Triggers: review simplicity, over-engineering, complexity check, YAGNI.
Valida uso correto de design tokens do projeto Nossa Maternidade. Detecta cores hardcoded (#FFFFFF, rgba), spacing hardcoded, e sugere tokens corretos. Use ao revisar codigo de UI, criar componentes, ou validar design system.
Zenn่จไบใฎMarkdownๆ กๆญฃใ่กใในใญใซใ่จไบใ่ชญใฟใZenn็ฌ่ช่จๆณใฎๆญฃ็ขบๆงใป่ฆๅบใๆง้ ใปใณใผใใใญใใฏใปใชใณใฏใป็ปๅใปใใผใใซใปๅใ่พผใฟใปใกใใปใผใธ/ใขใณใผใใฃใชใณ่จๆณใใใงใใฏใใๆนๅๆๆกใ่กใใใฆใผใถใผใใZenn่จไบใๆ กๆญฃใใฆใใZennใฎ่จๆณใใใงใใฏใใฆใใ่จไบใใฌใใฅใผใใฆใใMarkdown็ขบ่ชใใฆใใจไพ้ ผใใ้ใซไฝฟ็จใใใ
Performs a fast, focused code review checking for common issues, security vulnerabilities, and best practices without over-engineering. Optimized for cost-efficiency by targeting specific concerns rather than broad exploration.
Refactor and sanitize FastAPI codebases by removing dead code, enforcing Pydantic V2 standards, and running deterministic linters.
Verify errors are handled gracefully with meaningful user feedback. Issues result in WARNINGS.
AI ้ฉฑๅจ็ไปฃ็ ๅฎกๆฅ่ฝๅ๏ผๅฝ็จๆทๆๅฐไปฃ็ ๅฎกๆฅใcode reviewใๅฎกๆฅไปฃ็ ใๆฅ็ไปฃ็ ่ดจ้็ญๅ ณ้ฎ่ฏๆถ่ชๅจ่งฆๅใไฝฟ็จ 9 ไธชๅนถ่ก Agent ่ฟ่กๅ จ็ปดๅบฆๅๆ๏ผBug/่ดจ้/ๅฎๅ จ/ๆง่ฝ๏ผใ
Provides comprehensive coding standards for quality, naming conventions, error handling, concurrency, and memory management. Use when writing new code, reviewing code, fixing bugs, or refactoring existing code.
Auto-invoke when reviewing HTML head, meta tags, or Next.js page components. Enforces semantic HTML and search optimization.
Code review skill for quality, standards compliance, and best practices
Apply rustfmt and clippy linting standards for consistent, safe Rust code. Use before commits and in CI pipelines.
When building UI components, forms, or any user-facing interface. Check before every frontend PR.
Use when creating project rules, adding .claude/rules/*.md files, or scoping rules to specific files with globs for token efficiency.
Runs configured type checkers (pyrefly, mypy) on files after editing. MUST USE when validating Python type safety (Internal-only passive hook).
Validate codebase architecture and organization before releases. Use when user asks to 'check architecture', 'validate structure', 'pre-release check', or before versioning.