react-typescript-review
仓库创建 2026年7月26日最近提交 1 天前SkillHot 收录 1 天前
▸ 精选理由
专注关键缺陷与类型安全,显著节省人工审查时间。
这个 Skill 做什么
以资深前端工程师的视角审查 React + TypeScript 代码,聚焦正确性与类型安全。
以资深前端工程师的视角检查 React + TypeScript(TSX/JSX)代码,重点抓能真影响运行的 bug:hooks 问题、类型安全、性能和无障碍。适合审 PR、单个组件或粘贴的文件,遇到“这个组件对吗?”这种问题就用。不要把时间花在格式或风格争论上(Prettier/ESLint 处理这些),把精力放在会导致线上问题的地方。
▸ 展开 SKILL.md 英文原文
Review React + TypeScript code — components, hooks, a PR, or a pasted file — the way a senior frontend engineer would, prioritizing correctness, hooks bugs, performance, accessibility, and type safety over style nits. Use whenever the user asks you to review, critique, or check React/TSX/JSX code or a frontend PR, or asks "is this component right?" — even if they don't say "code review".
0
Stars
0
Forks
4
仓库内 Skill
积累中
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/jacobjustin8/skill-forge/main/examples/react-review/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/jacobjustin8/skill-forge/main/examples/react-review/SKILL.md"SKILL.MD 节选查看完整文件 ↗
# React + TypeScript review
Review the way a senior frontend engineer whose reviews people trust would: catch
the bugs that actually ship broken UI, and skip the bikeshedding. The goal is a
change that leaves the frontend healthier, with the author's time respected.
Prettier/ESLint already handle formatting — don't spend review on it.
## Review in priority order
Read every line you approve, but spend attention where the risk is highest.
1. **Hooks correctness — the #1 source of real React bugs.**
- Hooks must be called unconditionally at the top level — never inside
conditionals, loops, or nested functions. Flag any conditional hook.
- `useEffect` / `useCallback` / `useMemo` dvia SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有