Prompt file imported from jmagly/transcribe-cli (.claude/commands/pr-review.md). Fill in {{arguments}} before use. Copyright stays with the author.

PR Review

Name: pr-review
Author: jmagly

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.

Task 1: Product Manager Review

Objective: Assess from a product management perspective, focusing on:

Business Value: Does this PR clearly advance our core product goals and deliver immediate ROI?
User Experience: Is the change intuitive and delightful for users right now? If not, make fixes immediately.
Strategic Alignment: Does the PR align with current (and long-term, i.e., now) strategic objectives?

Action: Provide clear directives on how to ensure maximum user and business impact. All "future" suggestions must be implemented now.

Task 2: Developer Review

Objective: Evaluate the code thoroughly from a senior lead engineer perspective:

Code Quality & Maintainability: Is the code structured for readability and easy maintenance? If not, refactor now.
Performance & Scalability: Will these changes operate efficiently at scale? If not, optimize immediately.
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.

Task 3: Quality Engineer Review

Objective: Verify the overall quality, testing strategy, and reliability of the solution:

Test Coverage: Are there sufficient tests (unit, integration, E2E)? If not, add them now.
Potential Bugs & Edge Cases: Have all edge cases been considered? If not, address them immediately.
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.

Task 4: Security Engineer Review

Objective: Ensure robust security practices and compliance:

Vulnerabilities:

# PR Review **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**. --- ## Task 1: Product Manager Review **Objective**: Assess from a product management perspective, focusing on: - **Business Value**: Does this PR clearly advance our core product goals and deliver immediate ROI? - **User Experience**: Is the change intuitive and delightful for users right now? If not, make fixes immediately. - **Strategic Alignment**: Does the PR align with current (and long-term, i.e., now) strategic objectives? **Action**: Provide clear directives on how to ensure maximum user and business impact. All "future" suggestions must be implemented now. --- ## Task 2: Developer Review **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. --- ## Task 3: Quality Engineer Review **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. --- ## Task 4: Security Engineer Review **Objective**: Ensure robust security practices and compliance: 1. **Vulnerabilities**:

{ "prompt": "# PR Review\n\n**PR Link/Number**: {{arguments}}\n\n> **Instructions**: Execute each task in the order given to conduct a thorough code review. Update GitHub with this review.\n> **Important**: The future is now—any improvements or \"future\" recommendations must be addressed **immediately**.\n\n---\n\n## Task 1: Product Manager Review\n\n**Objective**: Assess from a product management perspective, focusing on:\n- **Business Value**: Does this PR clearly advance our core product goals and deliver immediate ROI?\n- **User Experience**: Is the change intuitive and delightful for users right now? If not, make fixes immediately.\n- **Strategic Alignment**: Does the PR align with current (and long-term, i.e., now) strategic objectives?\n\n**Action**: Provide clear directives on how to ensure maximum user and business impact. All \"future\" suggestions must be implemented now.\n\n---\n\n## Task 2: Developer Review\n\n**Objective**: Evaluate the code thoroughly from a senior lead engineer perspective:\n1. **Code Quality & Maintainability**: Is the code structured for readability and easy maintenance? If not, refactor now.\n2. **Performance & Scalability**: Will these changes operate efficiently at scale? If not, optimize immediately.\n3. **Best Practices & Standards**: Note any deviation from coding standards and correct it now.\n\n**Action**: Leave a concise yet complete review comment, ensuring all improvements happen immediately—no deferrals.\n\n---\n\n## Task 3: Quality Engineer Review\n\n**Objective**: Verify the overall quality, testing strategy, and reliability of the solution:\n1. **Test Coverage**: Are there sufficient tests (unit, integration, E2E)? If not, add them now.\n2. **Potential Bugs & Edge Cases**: Have all edge cases been considered? If not, address them immediately.\n3. **Regression Risk**: Confirm changes don't undermine existing functionality. If risk is identified, mitigate now with additional checks or tests.\n\n**Action**: Provide a detailed QA assessment, insisting any \"future\" improvements be completed right away.\n\n---\n\n## Task 4: Security Engineer Review\n\n**Objective**: Ensure robust security practices and compliance:\n1. **Vulnerabilities**:", "variables": [ "arguments" ], "notes": "Conduct comprehensive PR review from multiple perspectives (PM, Developer, QA, Security) Tools: Bash(gh *), Read. Arguments: <pr_link_or_number>.", "metadata": { "source": { "provider": "github-claude-commands", "repository": "https://github.com/jmagly/transcribe-cli", "path": ".claude/commands/pr-review.md", "ref": "ace92927f66596fbaaed2f53e2d0711f7a196a64", "url": "https://github.com/jmagly/transcribe-cli/blob/ace92927f66596fbaaed2f53e2d0711f7a196a64/.claude/commands/pr-review.md", "key": "jmagly/transcribe-cli/.claude/commands/pr-review.md" } } }

pr-review

About

PR Review

Task 1: Product Manager Review

Task 2: Developer Review

Task 3: Quality Engineer Review

Task 4: Security Engineer Review

Use it

Manifest

Reviews