npx claudepluginhub sultano/claude-code-marketplace --plugin sultano-toolkitUse `git status` to identify changed files, then thoroughly review all modified code. Review the code as if a senior engineer wrote it without over engineering and ensuring it follows these principles: - **SOLID**: Single responsibility, Open/closed, Liskov substitution, Interface segregation, Dependency inversion - **DRY**: Don't repeat yourself - eliminate code duplication - **KISS**: Keep it simple, stupid - avoid unnecessary complexity - **YAGNI**: You aren't gonna need it - don't add functionality until needed Check for: 1. Code quality and adherence to SOLID, DRY, KISS, YAGNI prin...
/code-reviewReviews local uncommitted changes or GitHub PRs (pass PR number/URL) for security vulnerabilities, code quality issues, and best practices. Generates severity-based report with file locations, descriptions, and fixes.
/code-reviewPerforms automated multi-agent code review on current GitHub pull request: audits CLAUDE.md, bugs, git history, prior PRs, code comments; scores issue confidence.
/code-reviewReviews uncommitted changes for security vulnerabilities, code quality issues, and best practices using git diff. Generates report with severity levels, locations, descriptions, fixes; blocks commits on critical/high issues.
/code-reviewPerforms comprehensive code quality review of repository structure, code, security, performance, architecture, testing, and documentation. Produces prioritized issues and actionable recommendations with examples.
/code-reviewPerforms comprehensive code quality review of repository structure, code, security, performance, architecture, testing, and documentation. Produces prioritized issues and actionable recommendations with examples.
/code-reviewPerforms holistic pre-push code review against design docs, analyzing diff and broader codebase for alignment, consistency, risks, and issues. Produces categorized findings with recommendations.
Use git status to identify changed files, then thoroughly review all modified code.
Review the code as if a senior engineer wrote it without over engineering and ensuring it follows these principles:
Check for:
Provide specific, actionable feedback with file paths and line numbers. Focus on meaningful improvements, not over-engineering.