pr-review

Analyze GitHub pull requests and run terminal smoke tests.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Heron11/otter-code --skill pr-review-heron11
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/Heron11/otter-code/tree/main/.qwen/skills/pr-review
Command: npx skills add https://github.com/Heron11/otter-code --skill pr-review-heron11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps pull request feedback reliable by combining targeted code reviews with deterministic terminal smoke testing, ensuring regressions and style issues are caught before merging.

Core Features & Use Cases

  • Structured evaluation of correctness, style, performance, test coverage, and security concerns using GitHub CLI data.
  • Terminal smoke testing that rebuilds the project, runs integration scenarios, and captures screenshots for reviewers.
  • Documentation workflow for uploading evidence via Playwright MCP so reviewers can see CLI behavior without reproducing it locally.

Quick Start

Ask the pr-review skill to fetch the PR diff, analyze the logic, and run the CLI smoke test before commenting.

Frequently Asked Questions about pr-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub PR code review and terminal smoke testing?

Automate GitHub PR code review and terminal smoke testing by fetching diffs via GitHub CLI, analyzing logic, running CLI integration scenarios, and capturing screenshot evidence. This ensures regressions and style issues are caught before merging.

What does terminal smoke testing evaluate during a pull request review?

Terminal smoke testing during a pull request review evaluates CLI behavior by rebuilding the project and running integration scenarios. It captures screenshots of terminal output to provide visual test evidence for reviewers without requiring local reproduction.

Do I need GitHub CLI access to run automated code review on pull requests?

Yes, you need GitHub CLI access to run automated code review on pull requests. The workflow fetches PR diff data and metadata through GitHub CLI, requiring npm build artifacts and terminal-capture scenarios to validate logic and generate screenshot uploads.

How to upload terminal screenshots as visual test evidence for code review?

Upload terminal screenshots as visual test evidence for code review by using Playwright MCP documentation workflows. The process captures terminal-capture scenarios during CLI smoke tests, allowing reviewers to see integration behavior without reproducing it locally.

Can terminal smoke testing catch security and performance issues before merge?

Terminal smoke testing and structured code analysis can catch security and performance issues before merge. The evaluation assesses correctness, style, performance, test coverage, and security concerns using GitHub CLI data to keep pull request feedback reliable.

What are the limitations of using CLI smoke tests for pull request validation?

Limitations of using CLI smoke tests for pull request validation include the requirement for npm build artifacts and terminal-capture scenarios. The process focuses on GitHub PRs and CLI-based validations, needing GitHub CLI access to fetch diffs and run integration scenarios.