five
Apply the Five Whys root cause analysis technique to investigate an issue
Run a multi-perspective PR review (product, dev, QA, security, DevOps, UX) and post it to GitHub
$ npx -y skills add wesammustafa/Claude-Code-Everything-You-Need-to-Know --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/reviewContext preview
What this command does when you run it.
Run a multi-perspective PR review (product, dev, QA, security, DevOps, UX) and post it to GitHub
name: review description: Run a multi-perspective PR review (product, dev, QA, security, DevOps, UX) and post it to GitHub
**PR Link/Number**: $ARGUMENTS
> **Instructions**: Execute each task in the order given to conduct a thorough code review. Update GitHub with this review. > **Important**: The future is now—any improvements or “future” recommendations must be addressed **immediately**.
---
**Objective**: Assess from a product management perspective, focusing on:
**Action**: Provide clear directives on how to ensure maximum user and business impact. All “future” suggestions must be implemented now.
---
**Objective**: Evaluate the code thoroughly from a senior lead engineer perspective: 1. **Code Quality & Maintainability**: Is the code structured for readability and easy maintenance? If not, refactor now. 2. **Performance & Scalability**: Will these changes operate efficiently at scale? If not, optimize immediately. 3. **Best Practices & Standards**: Note any deviation from coding standards and correct it now.
**Action**: Leave a concise yet complete review comment, ensuring all improvements happen immediately—no deferrals.
---
**Objective**: Verify the overall quality, testing strategy, and reliability of the solution: 1. **Test Coverage**: Are there sufficient tests (unit, integration, E2E)? If not, add them now. 2. **Potential Bugs & Edge Cases**: Have all edge cases been considered? If not, address them immediately. 3. **Regression Risk**: Confirm changes don’t undermine existing functionality. If risk is identified, mitigate now with additional checks or tests.
**Action**: Provide a detailed QA assessment, insisting any “future” improvements be completed right away.
---
**Objective**: Ensure robust security practices and compliance: 1. **Vulnerabilities**: Could these changes introduce security vulnerabilities? If so, fix them right away. 2. **Data Handling**: Are we properly protecting sensitive data (e.g., encryption, sanitization)? Address all gaps now. 3. **Compliance**: Confirm alignment with any relevant security or privacy standards (e.g., OWASP, GDPR, HIPAA). Implement missing requirements immediately.
**Action**: Provide a security assessment. Any recommended fixes typically scheduled for “later” must be addressed now.
---
**Objective**: Evaluate build, deployment, and monitoring considerations: 1. **CI/CD Pipeline**: Validate that the PR integrates smoothly with existing build/test/deploy processes. If not, fix it now. 2. **Infrastructure & Configuration**: Check whether the code changes require immediate updates to infrastructure or configs. 3. **Monitoring & Alerts**: Identify new monitoring needs or potential improvements and implement them immediately.
**Action**: Provide a DevOps-centric review, insisting that any improvements or tweaks be executed now.
---
**Objective**: Ensure optimal user-centric design: 1. **Visual Consistency**: Confirm adherence to brand/design guidelines. If not, adjust now. 2. **Usability & Accessibility**: Validate that the UI is intuitive and compliant with accessibility standards. Make any corrections immediately. 3. **Interaction Flow**: Assess whether the user flow is seamless. If friction exists, refine now.
**Action**: Provide a detailed UI/UX evaluation. Any enhancements typically set for “later” must be done immediately.
---
**End of PR Review**
From first prompt to agent teams — one guide. A practical guide to Claude Code — from your first prompt to multi-agent automation, hooks, MCP, and team workflows. Built around clear mental models and real examples, not marketing.
Repo: wesammustafa/Claude-Code-Everything-You-Need-to-Know
Apply the Five Whys root cause analysis technique to investigate an issue
Create a branch, split changes into logical commits, and open a pull request
Development practices and TDD workflow to follow before starting a feature
LLM unit testing best practices checklist for testing internal logic, not API endpoints
Manage project todos in todos.md file
User Experience Designer & UI Specialist persona for design-focused tasks