1k-code-review-pr

Detect build, script, CI, and docs issues in OneKey monorepo PRs.

3|3|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/OneKeyHQ/app-modules --skill 1k-code-review-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1k-code-review-pr
Source: https://github.com/OneKeyHQ/app-modules/tree/main/.claude/skills/1k-code-review-pr
Command: npx skills add https://github.com/OneKeyHQ/app-modules --skill 1k-code-review-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, actionable PR review checklist to quickly identify build, script, CI workflow gaps, and documentation inconsistencies in the OneKey monorepo. It helps reviewers deliver concrete feedback with clear priorities and suggested fixes.

Core Features & Use Cases

  • Accurate issue detection: Identify build failures, flaky scripts, CI gaps, and documentation omissions early in PR reviews.
  • Priority-guided remediation: Categorize findings by High/Medium/Low with specific fix suggestions.
  • Consistency across PRs: Standardize review quality for all changes affecting core packages and workflows.

Quick Start

Run a PR review using this skill on the current patch by following the checklist and generating a report that highlights critical issues, recommended fixes, and rationale. For example: fetch the PR diff with git fetch origin; compare origin/main...HEAD; apply the checklist to each changed file.

Frequently Asked Questions about 1k-code-review-pr

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

FAQPage Schema
How do I conduct a structured code review for pull requests?

A structured code review uses a standardized checklist to systematically evaluate PRs across build, scripts, CI workflows, and documentation. This approach ensures consistent feedback quality, identifies issues early, and provides reviewers with priority-based findings and concrete fix suggestions for each change.

What should I check for in PR reviews to catch build and CI failures?

PR reviews should verify build integrity, script quality, CI workflow configuration, and documentation completeness. A structured checklist catches build failures, flaky scripts, and CI gaps before merge, categorizing findings by priority with specific remediation steps for each issue type.

How do I standardize code review quality across multiple pull requests?

Standardize reviews by applying a consistent checklist template across all PRs affecting core packages and workflows. This enforces uniform coverage of build, script, CI, and documentation concerns, reducing reviewer variance and ensuring all changes meet the same quality bar.

Can I use a code review checklist for monorepo pull requests?

Yes, a structured PR review checklist works across monorepo changes affecting multiple core packages and workflows. It identifies build, script, CI, and documentation issues specific to interdependent components, prioritizes findings, and delivers actionable feedback aligned with monorepo complexity.

What's the difference between manual code review and a structured PR checklist?

Manual reviews rely on reviewer discretion and vary in coverage; structured checklists enforce consistent evaluation of build, scripts, CI, and docs across all PRs. Checklists reduce missed issues, standardize priority classification, and provide templated remediation guidance reviewers can apply uniformly.