github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination
Skills correspondant au nom, à la description ou à l’auteur GitHub.
Comprehensive GitHub code review with AI-powered swarm coordination
Code review guidelines covering code quality, security, and best practices.
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement...
Code review guidelines for general development and Rails projects. Provides reviewer personality, review perspectives, Rails-specific rules, and test quality standards. Use for code review, PR review, review co...
Enforce SOLID design principles during code generation, refactors, and code review (SRP/OCP/LSP/ISP/DIP). Use when changing architecture, introducing new abstractions, reducing coupling, eliminating type-switch...
M3社が開発したPythonの機械学習パイプラインツールgokartに関する深い知識とベストプラクティスを提供する。Use when reviewing gokart task designs, implementing type-safe ML pipelines, writing gokart tests, or workin...
Comprehensive code review focusing on quality, security, performance, and best practices. Use when reviewing PRs, commits, or code changes.
Pick up and implement the next available feature from /.agent-features/. Use when user says "develop feature", "work on next feature", "implement feature", or starts a new session to continue feature-driven dev...
code review feedback quality analysis best practices consistency checking
Perform code reviews following Python best practices. Use when reviewing pull requests, examining code changes, or providing feedback on code quality. Covers security, performance, testing, and design review.
Expert code reviewer for TypeScript + React 19 applications. Use when reviewing React code, identifying anti-patterns, evaluating state management, or assessing code maintainability. Triggers: code review reque...
Provides expert code quality analysis, technical debt assessment, and maintainability evaluation. Use this skill when the user needs code review, tech debt inventory, refactoring prioritization, or code health...
This skill should be used when the user asks to "triage an issue", "evaluate a feature request", "should I accept this issue", "analyze GitHub issue", "review this pull request", "review this PR", "should I mer...
Conducts comprehensive security code reviews including vulnerability detection (OWASP Top 10, CWE), authentication/authorization flaws, injection attacks, cryptography issues, sensitive data exposure, API secur...
Conducts comprehensive backend code reviews including API design (REST/GraphQL/gRPC), database patterns, authentication/authorization, caching strategies, message queues, microservices architecture, security vu...
Conducts comprehensive frontend code reviews including React/Vue/Angular component analysis, TypeScript/JavaScript quality assessment, CSS/styling review, performance optimization, accessibility compliance, sec...
Code review standards and best practices for Slotify project. Use this skill when reviewing code, suggesting improvements, or maintaining code quality. Covers TypeScript, React hooks, error handling, and securi...
執行提交前檢查(linting、測試、code review)並建立 git commit。當使用者說「commit」、「提交」、「幫我提交」時使用。
Orchestrate multi-agent development workflows. Use when starting a new feature to coordinate architecture design, implementation, code review, and release through specialized sub-agents.
Harsh code reviewer with functional programming bias. Blocks PRs to teach.
MUST BE USED for code review. Use PROACTIVELY when /review command is invoked or after any code changes to check correctness, architecture, and security.
Fix issues from code review. Use when the user invokes /fix or asks to address review findings for an issue.
Code review. Use when the user invokes /review or asks for a review of changes tied to an issue.
Code review for bugs, security, tenant isolation, RLS compliance, and maintainability. Reviews BOMvault code with focus on multi-tenancy safety and regulatory requirements.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.