review-checklist

Review LobeHub pull request diffs for correctness, security, testing, i18n, routing, reuse, database, and cloud issues.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/duwenji/generative-ai-oss-tutorials --skill review-checklist-duwenji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-checklist
Source: https://github.com/duwenji/generative-ai-oss-tutorials/tree/main/sandbox/lobe-chat/.agents/skills/review-checklist
Command: npx skills add https://github.com/duwenji/generative-ai-oss-tutorials --skill review-checklist-duwenji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers prevent recurring LobeHub pull request issues by providing a structured checklist that flags correctness, security, testing, i18n, routing, reuse, database safety, and cloud impact risks.

Core Features & Use Cases

  • Correctness & quality checks: Detects leftover console output, missing return/await patterns, and opportunities to simplify or improve compatibility.
  • Security and operational safeguards: Verifies that secrets are not exposed and that risky terminal output (like large base64 dumps) is avoided.
  • Delivery confidence and maintenance hygiene: Ensures tests cover fixes, i18n strings are handled via the expected locale key strategy, router configuration stays consistent, migrations are idempotent, and cloud-dependent changes are explicitly reviewed.

Quick Start

Review your PR diffs against this checklist to systematically identify the most common LobeHub mistakes before merging.

Frequently Asked Questions about review-checklist

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

FAQPage Schema
How do I review a LobeHub pull request for security and i18n risks?

Review LobeHub pull requests by applying a structured checklist to the PR diff to flag secret leakage, verify i18n locale key strategy, and enforce test coverage for security and internationalization risks.

What common code review mistakes cause database migration failures?

Common code review mistakes causing database migration failures include failing to ensure migrations are idempotent and not explicitly reviewing cloud-dependent changes, which a structured review checklist catches before shipping.

How do I ensure desktop router configurations stay consistent in code changes?

Ensure desktop router configurations stay consistent by reviewing branch changes to keep desktop router pairs aligned, preventing routing regressions when modifying router configs or UI components in pull requests.

Does this code review checklist work for backend SSR path changes?

Yes, this code review checklist works for backend SSR path changes by flagging backend and server-side rendering path risks, dependency impacts, and operational safeguards like risky terminal output within the PR diff.

How do I catch missing await patterns and leftover console output before merging?

Catch missing await patterns and leftover console output by running correctness and quality checks on feature work diffs to detect leftover console output, missing return statements, and await patterns before merging.