review-type-safety
Audit TypeScript code for type safety issues—any/unknown abuse, invalid states, missing narrowing.
Audit TypeScript code for type safety issues—any/unknown abuse, invalid states, missing narrowing.
Verify code changes comply with CLAUDE.md instructions and project standards.
Audits lint errors, type checks, dead code, and commit hygiene. Use when checking project health, running lint/type checks, or finding unused code.
validate_skills.pyを実行してSkills/Agents/Commandsの構文を検証し、エラーを修正してログを記録する。「バリデーション」「構文検証」「Skillsチェック」を依頼されたときに使用する。
Audit code for logical bugs, race conditions, edge cases, and error handling issues.
validate_skills.pyを実行してSkills/Agents/Commandsの構文を検証し、エラーを修正してログを記録する。「バリデーション」「構文検証」「Skillsチェック」を依頼されたときに使用する。
Audit code for DRY violations, dead code, complexity, and consistency issues.
Essential guidelines for writing modern, type-safe, and idiomatic Python 3 code.
Reviews code for security vulnerabilities. Use when implementing auth, handling user input, adding APIs, or before deployment. Checks OWASP Top 10, credentials, injection.
Select and configure appropriate Azure RBAC roles following the principle of least privilege for secure access control
Security analyst persona with deep OWASP expertise, vulnerability classification, risk assessment, and compliance mapping
Security best practices (OWASP Top 10) and testing strategies for software development. Covers secure coding, vulnerability prevention, testing pyramid, API design, and observability patterns. Use when reviewing code for security, writing tests, designing APIs, or when asking about security vulnerabilities, testing strategies, logging, or monitoring.
Validates constitution status before executing /flowspec commands. Enforces tier-based validation rules (Light=warn, Medium=confirm, Heavy=block).
OWASPの基本を前提に、デフォルト安全(入力検証/認可/秘密情報/監査ログ/SSR/CSRF等)を落とさずに設計・実装・レビューする。脅威と攻撃面を洗い出し、最小権限と安全な失敗で守るために使う。
Production-grade security testing with agentic vulnerability detection, SAST/DAST tools, OWASP Top 10 coverage, threat modeling, and AI-powered security analysis achieving 92% detection accuracy (OpenAI Aardvark benchmark 2024)
WHEN to auto-invoke: Writing E2E tests, browser automation, Playwright tests, visual regression testing, integration testing, test file creation (*.test.ts, *.spec.ts), testing user flows. WHEN NOT to invoke: Unit tests for pure functions, API-only testing, database testing, documentation, non-testing implementation work.
Write and run unit tests for WoW addons using Busted and the Mechanic test framework. Covers test structure, mocking WoW APIs, and coverage analysis. Use when adding tests, fixing bugs with regression tests, or improving coverage. Triggers: test, unit test, coverage, Busted, mock, TDD, sandbox.
Comprehensive visual regression testing using Playwright and jest-image-snapshot. Implements screenshot comparison, baseline management, CI/CD integration, and visual diff reporting following Ant Design best practices. Use for preventing visual bugs, ensuring UI consistency, and automating visual QA. (project)