pull-request-review
Review PR Comments
Target PR: $ARGUMENTS
If no argument provided, prompt the user for a PR link or number.
Step 1: Gather Requirements
- Fetch PR metadata and comments using the GitHub CLI:
gh pr view $ARGUMENTS --json number,title,body,reviews,comments gh api repos/{owner}/{repo}/pulls/{pr_number}/comments - Extract each unresolved review comment:
- Comment ID
- File path
- Line number
- Comment body
- Author
If no unresolved comments exist, report success and exit.
Step 2: Create Plan
In plan mode, create a plan that includes the following details:
Implement PR review feedback for $ARGUMENTS.
## PR Overview
- Title: [PR title]
- Description: [PR description summary]
## Review Comments to Address (ordered by file)
### 1. [file_path]:[line_number] (Comment ID: [id])
**Reviewer**: [author]
**Comment**: [full comment body]
**Action Required**: [brief description of what needs to change]
### 2. [file_path]:[line_number] (Comment ID: [id])
**Reviewer**: [author]
**Comment**: [full comment body]
**Action Required**: [brief description of what needs to change]
...
## Implementation Guidelines
- Evaluate each comment for validity before implementing
- If a comment is not valid, document the reasoning
- Ensure changes follow project coding standards
- Run relevant tests to verify changes work
## Acceptance Criteria
- All valid review comments addressed
- Tests pass after changes
- `bun run lint` passes
## Verification
Command: `bun run lint && bun run test`
Expected: All checks pass
More from codyswanngt/lisa
claude-code-action
Knowledge base for creating and configuring Claude Code Action GitHub workflows
43lisa-review-project
This skill should be used when comparing Lisa's source templates against a target project's implementation to identify drift. It validates the Lisa directory, detects project types, scans template directories, compares files, categorizes changes, and offers to adopt improvements back into Lisa. This is the inverse of lisa:review-implementation.
39lisa-integration-test
This skill should be used when integration testing Lisa against a downstream project. It applies Lisa templates, verifies the project still builds, and if anything breaks, fixes the templates upstream in Lisa and retries until the project passes all checks.
37lisa-learn
This skill should be used when analyzing a downstream project's git diff after Lisa was applied to identify improvements that should be upstreamed back to Lisa templates. It validates the environment, captures the diff, correlates changes with Lisa template directories, categorizes each change, and offers to upstream improvements.
35jsdoc-best-practices
Enforces JSDoc documentation standards for this TypeScript project. This skill should be used when writing or reviewing TypeScript code to ensure proper documentation with file preambles, function docs, interface docs, and the critical distinction between documenting "what" vs "why". Use this skill to understand the project's JSDoc ESLint rules and established patterns.
34plan-lower-code-complexity
This skill should be used when reducing the cognitive complexity threshold of the codebase. It lowers the threshold by 2, identifies functions that exceed the new limit, generates a brief with refactoring strategies, and creates a plan with tasks to fix all violations.
23