domain-driven-design
Use when planning features that involve business logic or domain modeling, and during code review to check naming consistency and module boundary violations — applies strategic DDD patterns
Bash Script Reviewer
Reviews shell scripts for Clean Code, SOLID, DRY, KISS, and YAGNI violations. Use when the user requests script review, mentions bash/shell code quality, or wants to fix script issues.
fresh-eyes-review
Use when about to commit, create a PR, or declare work complete — after verification-before-completion confirms tests pass but before code ships. Catches security vulnerabilities, logic errors, and business rule bugs that slip through despite passing tests.
review-vue
Review Vue 3 code for Composition API, reactivity, components, state (Pinia), routing, and performance. Framework-only atomic skill; output is a findings list.
file-todos
This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
review-changes
Code review of current git changes, compare to related plan if exists, identify bad engineering, over-engineering, or suboptimal solutions. Use when user asks to review changes, check git diff, validate implementation quality, or assess code changes.
_accessibility
Accessible markup, ARIA patterns, keyboard navigation, and inclusive design. Apply when writing or reviewing UI code.
OpenRouter Known Pitfalls
Help avoid common OpenRouter mistakes and anti-patterns. Use when reviewing code or onboarding developers. Trigger with phrases like 'openrouter pitfalls', 'openrouter mistakes', 'openrouter gotchas', 'openrouter common issues'.
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
convolutional-debate-agent
Multi-model reasoning protocol for Claude Code that runs five independent solver drafts (across different LLM providers), four adversarial debate reviews, and a reliability-weighted aggregation step to select or synthesize the final answer. Invoked via /debate slash command.
react-review
Review React code for useEffect misuse, convention violations, memoization issues, and architectural problems. Runs react-doctor, Haiku subagents for mechanical checks, and deep Sonnet analysis in parallel. Use when reviewing React components, finishing a feature, or refactoring.
Angular Best Practices
Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.
architect-review
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
solidity-audit
Security audit and code review checklist. Covers 30+ vulnerability types with real-world exploit cases (2021-2026) and EVMbench Code4rena patterns. Use when conducting security audits, code reviews, or pre-deployment security assessments.
Code Review
Perform code reviews following Sentry engineering practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
review
Quality review and accessibility audit workflow: severity-based findings, structured Markdown output, fix planning. Use when running /quality-review, /accessibility-audit, reviewing code quality, or auditing accessibility compliance. Triggers: review, audit, quality, accessibility, a11y, findings, severity.
code-review-checklist
체크리스트 기반 코드 리뷰 - 기능, 설계, 테스트, 보안, 성능
review
Multi-perspective code review using parallel agents. Consolidates findings by severity for user approval. Use when implementation is complete (/execute finished), user says "review", "code review", or "check the code", before creating a PR, or after significant changes.
multi-agent-reviewer
多Agent审查阶段。使用测试工程师编写测试用例,审查代码质量。 Activate when user wants to review code or write tests.
90-04-review
Run a composite, layered code review. Use when a coordinator needs to evaluate implementation quality before passing the quality gate. Stacks a 6-pass base rubric with optional language, architecture, and spec-divergence layers. Produces a tk review ticket with score and changes_requested.
Java Developer
Expert Java development skill covering Spring Boot, Jakarta EE, and plain Java across versions Java 8 through Java 21+. Use when asked to write, generate, review, architect, or improve Java code. Handles: creating REST APIs, designing domain models, generating boilerplate (entities, repositories, services, controllers), code review for correctness/scalability/security, performance optimization, JVM tuning guidance, concurrency patterns, and applying architecture patterns (layered, hexagonal, DDD). Triggers on any Java programming request.
pr-comment-resolver
Use this agent when you need to address comments on pull requests or code reviews by making the requested changes and reporting back on the resolution. This agent handles the full workflow of understanding the comment, implementing the fix, and providing a clear summary of what was done.