review-checklist

Review LobeHub pull request diffs for correctness, security, and architectural conventions.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kingheu0818-sketch/lobehub_yu --skill review-checklist-kingheu0818-sketch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-checklist
Source: https://github.com/kingheu0818-sketch/lobehub_yu/tree/main/.agents/skills/review-checklist
Command: npx skills add https://github.com/kingheu0818-sketch/lobehub_yu --skill review-checklist-kingheu0818-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers systematically spot recurring LobeHub-specific issues before they land in main, reducing bugs, security risks, and UI/route regressions.

Core Features & Use Cases

  • Correctness checks: Finds leftover console/debug output, missing return-await in try/catch, and opportunity for clearer, more compatible implementations.
  • Security checks: Flags sensitive data exposure, unsafe terminal output patterns (e.g., huge base64), and hardcoded secrets.
  • LobeHub-specific compatibility checks: Verifies desktopRouter pair updates, enforces i18n key usage, and recommends the correct UI stack (antd vs @lobehub/ui) and style system (antd-style tokens).

Quick Start

Use the review-checklist skill to evaluate a PR diff and confirm there are no routing drifts, i18n violations, security leaks, or non-idempotent migrations.

Frequently Asked Questions about review-checklist

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

FAQPage Schema
How do I check a LobeHub pull request for common code review mistakes?▼

A code review checklist for LobeHub PRs systematically evaluates diffs to catch routing drifts, i18n violations, security leaks, and non-idempotent database migrations, ensuring correctness, security, and architectural compliance.

What is the best way to verify database migration safety in a pull request?▼

Verifying database migration safety requires checking PR diffs for idempotent migration requirements, ensuring scripts execute consistently without side effects, preventing data corruption during deployment.

How does a code review checklist handle security and sensitive data exposure?▼

Security and sensitive data exposure checks flag hardcoded secrets, unsafe terminal output patterns, and sensitive data in logs, enforcing safe logging practices and preventing information leakage.

Do I need to update desktop routing and i18n keys together in LobeHub PRs?▼

Yes, LobeHub PRs require consistent desktopRouter pair updates and enforced i18n key usage to prevent UI and route regressions, ensuring architectural conventions are maintained.

Can I use antd components and styles instead of @lobehub/ui in LobeHub?▼

LobeHub compatibility checks validate UI component selection between antd and @lobehub/ui, enforcing antd-style tokens for the style system to maintain visual and architectural consistency.

What common coding errors does a PR review checklist catch?▼

Correctness checks identify leftover console or debug output, missing return-await in try/catch blocks, and implementation clarity opportunities, ensuring cleaner, more compatible code.