type-system-governance
Enforce TypeScript type organization rules. Use when creating types, interfaces, or DTOs. All types MUST go in /types directory - never inline in components.
Enforce TypeScript type organization rules. Use when creating types, interfaces, or DTOs. All types MUST go in /types directory - never inline in components.
Analyze code changes for security vulnerabilities using LLM reasoning and threat model patterns. Use for PR reviews, pre-commit checks, or branch comparisons.
Conducts comprehensive frontend code reviews including React/Vue/Angular component analysis, TypeScript/JavaScript quality assessment, CSS/styling review, performance optimization, accessibility compliance, security vulnerabilities, and best practices validation. Produces detailed review reports with specific issues, severity ratings, and actionable recommendations. Use when reviewing frontend code, analyzing React/Vue/Angular components, checking JavaScript/TypeScript quality, validating CSS/SCSS, assessing web performance, or when users mention "review frontend code", "check React components", "analyze JavaScript", "review TypeScript", "validate accessibility", or "frontend code quality".
Guide for security tooling (analyzers, fuzzers, decompilers, compilers) and consistent placement in README.md.
Import conventions and ordering rules. Use when writing imports or organizing import statements. Enforces explicit named imports, never wildcards.
Skill para revisar codigo com checklist de qualidade
Automatically fix ESLint errors by modifying code to comply with linting rules. For small codebases (≤20 errors), fixes directly. For larger codebases (>20 errors), spawns parallel agents per directory for efficient processing. Never disables rules or adds ignore comments.
Comprehensive code review guidelines for React 19 TypeScript projects
C++23 best practices with Google Test 1.15, clang-format 19, and modern C++ standards.
Senior Frontend Code Reviewer with 12+ years JavaScript/TypeScript experience. Use when reviewing React/TypeScript code, checking code quality and style, verifying accessibility compliance, ensuring test coverage, or configuring linting tools (ESLint, Prettier).
Python coding standards for Amplifier including type hints, async patterns, error handling, and formatting. Use when writing Python code for Amplifier modules.
Python code quality with ruff (linting & formatting) and mypy (type checking). Covers pyproject.toml configuration, pre-commit hooks, and type hints. Use when user mentions ruff, mypy, linting, formatting, type checking, code style, or Python code quality.
Validates PHP test files for CakePHP projects, ensuring compliance with testing standards including proper documentation format, Configure::read usage, and avoiding prohibited patterns
Review methodology for code changes with confidence scoring.
Run before marking coding tasks complete - validates code quality via IDE diagnostics, code review rules, and tests with fast-feedback short-circuiting
Structured code review approach covering security, quality, performance, and consistency.
Checks QMD files for consistency, variable references, and cross-format links. Use after batch editing multiple files or before commits.
Activates when user wants code reviewed for quality, best practices, bugs, or improvements. Triggers on "review this code", "check my implementation", "is this code good", "find bugs", "improve this function", "code quality check", or requests for feedback on code.
Validates beads issues after creation. Checks dependencies, PRD mapping, order. Use when: after creating issues in project-init, before TDD loop. Triggers: "validate beads", "check issues", "verify tasks".
Automatically choose the best output style (tables, bullets, YAML, HTML, concise) to improve scanability and save tokens
Obsidian 커뮤니티 플러그인 코드가 공식 가이드라인을 준수하는지 자동으로 검사하고 개선점을 제안하며, 플러그인 제출 전 코드 품질, 보안, 성능 검토가 필요할 때 사용한다.
Pre-merge security validation detecting secrets, user-specific paths, insecure SSH configurations, and security-weakening flags. Use before committing code/documentation, before creating PRs, or during QA validation. Supports automated scanning with severity-based enforcement (CRITICAL blocks merge, HIGH requires fixes).