Code review skills

Non-interactive wrapper over pr-review that emits JSON assessing whether a PR is ready for a human maintainer's time.

Review Clojure and ClojureScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs...

Review TypeScript and JavaScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs...

Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

This skill should be used when the user asks to "review STM32 code", "check my firmware", "find bugs in embedded code", "validate peripheral initialization", "audit interrupt...

Library-agnostic Flutter/Dart code review checklist covering widget best practices, state management patterns (BLoC, Riverpod, Provider, GetX, MobX, Signals), Dart idioms,...

Real-time structural Code Health via CodeScene MCP — review before edits, verify score deltas after changes, gate commits and PRs. Use when reviewing code quality, refactoring,...

库无关的Flutter/Dart代码审查清单，涵盖Widget最佳实践、状态管理模式（BLoC、Riverpod、Provider、GetX、MobX、Signals）、Dart惯用法、性能、可访问性、安全性和整洁架构。

ウィジェットのベストプラクティス、状態管理パターン（BLoC、Riverpod、Provider、GetX、MobX、Signals）、Dartのイディオム、パフォーマンス、アクセシビリティ、セキュリティ、クリーンアーキテクチャをカバーするライブラリに依存しないFlutter/Dartのコードレビューチェックリスト。

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec...

Use before you accept a change, to look at the actual diff with fresh eyes against the original goal and catch what's risky, half-done, or off-scope. Trigger when the user says...

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Clawtributor PRs here, last week or another window: discover conversation refs, recheck GitHub, rank by impact.

Review PyTorch pull requests for code quality, test coverage, security, and backward compatibility. Use when reviewing PRs, when asked to review code changes, or when the user...

Use only when the user explicitly requests a review or audit of backend code under . Supports pending-change, file-focused, and pasted-diff reviews. Do not use for...

Use only when the user explicitly requests a review or audit of frontend code under or . Supports pending-change, file-focused, and pasted-diff reviews. Do not use for...

Checks if a community pull request is ready for human review. Verifies CLA signature, PR title format, description completeness, test coverage, and cubic-dev-ai issues, then...

Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs,...

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and...

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Guidelines and tools for reviewing pull requests in the Angular repository.

Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.

风险审阅助手适合technical、管理者、software、API文档在用户提出“这里有什么风险”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。