Frontend Code Review
ProgrammerAnthony/Expert-Coding-Harness
A skill your agent uses when 用户需要审查前端代码（React/Vue/Next.js/TypeScript/Tailwind等）、检查代码质量、性能问题、可维护性、安全漏洞、最佳实践落地时。触发场景：前端代码评审、前端代码优化、React/Vue代码检查、TypeScript代码审查、前端性能优化、前端安全审计、前端代码规范检查。
指导在项目中对前端代码（Next.js/React/TypeScript/Tailwind 等）进行结构、可维护性、性能与一致性审查，基于既定规则清单。适用于用户请求审查 .tsx/.ts/.js/.jsx 等前端文件或前端目录下的页面与组件。不用于后端代码（如 .py）。
Install Frontend Code Review
$ npx skills add ProgrammerAnthony/Anything-Extract --skill frontend-code-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ProgrammerAnthony/Anything-Extract frontend-code-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Anything-Extract.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/frontend-code-review .claude/skills/frontend-code-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "frontend-code-review" agent skill from https://github.com/ProgrammerAnthony/Anything-Extract/tree/master/.agents/skills/frontend-code-review into .claude/skills/frontend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-code-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ProgrammerAnthony/Anything-Extract/tree/master/.agents/skills/frontend-code-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ProgrammerAnthony/Anything-Extract --skill frontend-code-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ProgrammerAnthony/Anything-Extract frontend-code-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Anything-Extract.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/frontend-code-review .agents/skills/frontend-code-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "frontend-code-review" agent skill from https://github.com/ProgrammerAnthony/Anything-Extract/tree/master/.agents/skills/frontend-code-review into .agents/skills/frontend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-code-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ProgrammerAnthony/Anything-Extract --skill frontend-code-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ProgrammerAnthony/Anything-Extract frontend-code-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Anything-Extract.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/frontend-code-review .cursor/skills/frontend-code-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "frontend-code-review" agent skill from https://github.com/ProgrammerAnthony/Anything-Extract/tree/master/.agents/skills/frontend-code-review into .cursor/skills/frontend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-code-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ProgrammerAnthony/Anything-Extract.git --path .agents/skills/frontend-code-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ProgrammerAnthony/Anything-Extract --skill frontend-code-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ProgrammerAnthony/Anything-Extract frontend-code-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Anything-Extract.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/frontend-code-review .gemini/skills/frontend-code-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "frontend-code-review" agent skill from https://github.com/ProgrammerAnthony/Anything-Extract/tree/master/.agents/skills/frontend-code-review into .gemini/skills/frontend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-code-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ProgrammerAnthony/Anything-Extract frontend-code-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ProgrammerAnthony/Anything-Extract --skill frontend-code-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Anything-Extract.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/frontend-code-review .github/skills/frontend-code-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "frontend-code-review" agent skill from https://github.com/ProgrammerAnthony/Anything-Extract/tree/master/.agents/skills/frontend-code-review into .github/skills/frontend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-code-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ProgrammerAnthony/Anything-Extract --skill frontend-code-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ProgrammerAnthony/Anything-Extract frontend-code-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ProgrammerAnthony/Anything-Extract.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/frontend-code-review .opencode/skills/frontend-code-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "frontend-code-review" agent skill from https://github.com/ProgrammerAnthony/Anything-Extract/tree/master/.agents/skills/frontend-code-review into .opencode/skills/frontend-code-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "frontend-code-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
frontend-code-review- GitHub stars
- 139
- Token cost
- ~957 tokens
- SKILL.md length
- 205 words
- Files
- 5 (incl. references)
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
指导在项目中对前端代码（Next.js/React/TypeScript/Tailwind 等）进行结构、可维护性、性能与一致性审查，基于既定规则清单。适用于用户请求审查 .tsx/.ts/.js/.jsx 等前端文件或前端目录下的页面与组件。不用于后端代码（如 .py）。
- Works in 4 steps: 明确审查范围与模式：根据用户输入，限定在指定的组件、页面或目录内，不要「全仓库漫扫… → 按 Checklist… → 若某段代码未被 Checklist 覆盖，可参考 General Review… → …
- Tasks that involve React components
- SKILL.md covers 何时使用本 Skill, 如何使用本 Skill, 项目前端结构（审查范围参考） and Checklist, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Frontend Code Review is an agent skill from ProgrammerAnthony/Anything-Extract. 指导在项目中对前端代码（Next.js/React/TypeScript/Tailwind 等）进行结构、可维护性、性能与一致性审查，基于既定规则清单。适用于用户请求审查 .tsx/.ts/.js/.jsx 等前端文件或前端目录下的页面与组件。不用于后端代码（如 .py）。
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/code-quality-rule.md`, `references/layout-style-rule.md` and `references/performance-rule.md`).
It sits in Frontend & Design, covering React components, CSS and styling and Code review. It works with Tailwind CSS, TypeScript, Next.js and React. The repository describes itself as: 高效文档识别&知识库&本地启动，前后端；整合QAnything、dify等思想和源码，快速批量可靠提取文档关键信息并导出. The licence is MIT.
When your agent uses it
- Tasks that involve React components
- Tasks that involve CSS and styling
- Tasks that involve Code review
Example prompts
- “/frontend-code-review”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 明确审查范围与模式：根据用户输入，限定在指定的组件、页面或目录内，不要「全仓库漫扫」。
- 按 Checklist 中的规则执行审查；对每条命中的规则，找到具体代码位置并给出可执行建议。
- 若某段代码未被 Checklist 覆盖，可参考 General Review Rules 做尽力审查。
- 输出时必须严格遵循「Required Output」中的模板之一。
What it can do on your machine
Read from SKILL.md and the folder at commit f1ed557. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Frontend Code Review loads about 957 tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 40 tokens; SKILL.md has 205 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ProgrammerAnthony/Anything-Extract at commit f1ed557, republished under its MIT licence (© ProgrammerAnthony). 205 words, ~957 tokens.
Download SKILL.mdSave it as
.claude/skills/frontend-code-review/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- frontend-code-review
- description
- 指导在项目中对前端代码（Next.js/React/TypeScript/Tailwind 等）进行结构、可维护性、性能与一致性审查，基于既定规则清单。适用于用户请求审查 .tsx/.ts/.js/.jsx 等前端文件或前端目录下的页面与组件。不用于后端代码（如 .py）。
Frontend Code Review（前端代码审查）
何时使用本 Skill
当用户要求审查、分析或改进前端代码（例如 .tsx、.ts、.js 文件）时使用本 skill。常见场景包括：
- 待提交变更审查：在提交前检查当前变更中涉及的前端文件。
- 代码片段审查：用户粘贴某个组件/页面/Hook 片段，请求审查。
- 按文件/模块审查：用户点名一到数个前端文件或某个路由/组件目录。
以下情况不要使用本 skill：
- 审查目标是后端代码（如
.py、服务层、数据库访问等）——此时应使用后端 Code Review Skill。 - 仅讨论架构文档或后端接口设计，而非前端实现。
如何使用本 Skill
- 明确审查范围与模式：根据用户输入，限定在指定的组件、页面或目录内，不要「全仓库漫扫」。
- 按 Checklist 中的规则执行审查；对每条命中的规则，找到具体代码位置并给出可执行建议。
- 若某段代码未被 Checklist 覆盖，可参考 General Review Rules 做尽力审查。
- 输出时必须严格遵循「Required Output」中的模板之一。
注意：
- 优先给出具体、可落地的改进建议（包括何处拆分组件、如何组织状态、如何统一样式等）。
- 若能提供简短代码示例，可帮助后续自动修复。
项目前端结构（审查范围参考）
以典型的 Next.js App Router + React + TypeScript + Tailwind 项目为例，常见分层与职责如下（实际路径以当前仓库为准，可根据项目实际结构类比到对应目录）：
- 路由与页面入口目录（例如
app/或frontend/app/）：- 路由与页面入口（如
app/xxx/page.tsx、app/[id]/page.tsx等）。 - 顶层布局（如
layout.tsx），通常挂载全局布局组件（主框架、侧边栏、头部），不要在此堆积业务逻辑。
- 路由与页面入口（如
- 通用与领域组件目录（例如
components/或frontend/components/）：- 复用的布局组件（如页面头部、布局容器）、表格/卡片/表单等 UI 组件。
- 领域组件（如知识库列表、文档分段列表、业务向导步骤组件等），负责组合 UI 与轻量交互。
lib/或services/：- HTTP 客户端与前端 API 封装（如 axios 实例、领域 API 模块）。
- 通用工具函数与 Hook（如复用的数据加载 Hook、格式化工具等）。 -- 样式配置：
- 全局样式（如
app/globals.css）用于基础样式、滚动条、字体等。 - Tailwind 配置（如
tailwind.config.js）可扩展主题颜色、间距、阴影等设计令牌，避免散落魔法值。
在进行前端 Code Review 时，优先检查：
- 页面是否复用了现有布局组件与上下文（例如统一的页面头部组件、侧边栏折叠状态的上下文），而不是各自实现一套布局。
- 新增页面是否放在合理的路由目录（与现有路由结构保持一致），新增组件是否放在组件目录下的合适子目录，而不是全部堆在页面文件中。
- 数据请求是否统一走封装好的 API 层或服务模块，而不是在组件内重复配置 axios/fetch。
Checklist
根据审查范围，优先按以下规则文件进行检查：
- 代码质量与组件设计：若涉及组件/Hook/页面结构、TypeScript 类型、可维护性，参考 references/code-quality-rule.md。
- 布局、样式与 UI 一致性：若涉及布局框架、全局样式、颜色与风格统一、响应式表现，参考 references/layout-style-rule.md。
- 状态管理与数据流：若涉及本地/全局状态、表单状态、异步数据加载、API 错误处理，参考 references/state-data-rule.md。
- 性能与交互体验：若涉及渲染性能、大列表、客户端/服务端边界、懒加载、交互反馈，参考 references/performance-rule.md。
若 Checklist 中的规则均不适用，可退回到下文的 General Review Rules 做尽力审查。
General Review Rules
从以下四个维度给出审查意见：
结构与可维护性
- 组件/页面是否职责单一，可读性良好，便于拆分与复用。
- 是否存在重复代码（卡片、按钮、列表等模式），可以抽成复用组件。
- 类型是否清晰（尽量避免
any），关键数据结构是否有统一的接口/类型定义。
布局、样式与一致性
- 是否复用统一的布局组件（主布局、页面头部、侧边栏等）。
- Tailwind 类名是否过度堆叠、包含大量魔法色值（如随意使用类似但不一致的灰色/紫色）。
- 是否存在同一业务模块内风格不统一的问题（按钮样式、圆角、间距等）。
状态与数据
- 异步请求是否有完整的 loading / error / empty 状态反馈。
- 状态是否放在合适的层级（避免过度提升或不必要的全局状态）。
- 是否存在可以用派生值计算的状态被重复存储的问题。
性能与用户体验
- 是否有不必要的重新渲染（例如在
.map中频繁创建匿名函数或对象、缺少 key 或 key 不稳定）。 - 大列表/复杂视图是否考虑了懒加载、分页或虚拟列表。
- 交互是否有明确反馈（按钮禁用/加载中的样式、错误提示等）。
- 是否有不必要的重新渲染（例如在
Required Output
当调用本 skill 时，输出必须严格遵循下列两种模板之一。
Template A（存在问题或改进建议时）
# Code review
Found <N> urgent issues need to be fixed:
## 1 <brief description of bug>
FilePath: <path> line <line>
<relevant code snippet or pointer>
### Suggested fix
<brief description of suggested fix>
---
... (repeat for each urgent issue) ...
Found <M> suggestions for improvement:
## 1 <brief description of suggestion>
FilePath: <path> line <line>
<relevant code snippet or pointer>
### Suggested fix
<brief description of suggested fix>
---
... (repeat for each suggestion) ...要求：
- 若没有「紧急问题」，可以省略
urgent issues段落。 - 若没有「建议」，可以省略
suggestions for improvement段落。 - 若问题数量超过 10 条，可汇总为 "10+ urgent issues" / "10+ suggestions"，并仅输出前 10 条。
- 保持模板中的空行与分隔线格式，以便后续自动解析。
- 若使用 Template A，且至少有一条需要改代码的项，最后追加一句简短追问，例如：
Would you like me to use the Suggested fix section to address these issues?
Template B（未发现问题时）
## Code review
No issues found.© ProgrammerAnthony, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in .agents/skills/frontend-code-review of ProgrammerAnthony/Anything-Extract.
- SKILL.md
- references/code-quality-rule.md
- references/layout-style-rule.md
- references/performance-rule.md
- references/state-data-rule.md
Open the folder on GitHubat commit f1ed557
Compare with similar skills
Frontend Code Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Frontend Code Review this skillProgrammerAnthony/Anything-Extract | 139 | — | ~957 | Automated safety check: Pass | MIT | |
| Frontend Code ReviewProgrammerAnthony/Expert-Coding-Harness | 235 | — | ~614 | Automated safety check: Pass | MIT | |
| Bmm Iconify IconsY80/bmm | 343 | — | ~810 | Automated safety check: Pass | MIT | |
| Shadcn Tailwind UILiarMTTT/TavernWeave | 148 | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Dokan Frontend Devgetdokan/dokan | 288 | — | ~1.9k | Automated safety check: Pass | None | |
| Oma Frontendfirst-fluke/oh-my-agent | 1.3k | — | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
Bmm Iconify Icons
Y80/bmm
Guide for updating Iconify icons and IconNames conventions in BMM.
Shadcn Tailwind UI
LiarMTTT/TavernWeave
Build, restyle, or review accessible React interfaces that use shadcn/ui, Radix UI primitives, and Tailwind CSS.
Dokan Frontend Dev
getdokan/dokan
Add or modify Dokan frontend code (React, TypeScript, Vue, Tailwind).
Oma Frontend
first-fluke/oh-my-agent
Frontend specialist for React, Next.js, TypeScript with FSD-lite architecture, shadcn/ui, and design system alignment.
Frontend Development
avibebuilder/claude-prime
A skill your agent uses for ANY work involving React, Next.js, TypeScript, or Tailwind in the browser layer.
More from ProgrammerAnthony/Anything-Extract
All 13 skills in this repoBackend Code Review
ProgrammerAnthony/Anything-Extract
指导在项目（python项目）中队后端代码进行质量、安全、可维护性与最佳实践审查，基于既定规则清单。适用于用户请求对 backend/ 下后端文件（如 .py）进行审查、分析或改进。不用于前端文件（如 .tsx、.ts、.js）。支持待提交变更审查、代码片段审查、按文件审查。
Design An Interface
ProgrammerAnthony/Anything-Extract
使用并行子 agent 为某个模块生成多个根本不同的接口设计。适用于用户希望设计某个 API、探索接口选项、对比模块形状（module shapes），或提到“design it twice（把它设计两遍）”。
TDD
ProgrammerAnthony/Anything-Extract
使用 RED-GREEN-重构（red-green-refactor）循环进行测试驱动开发。适用于用户希望用 TDD 构建新功能或修复 bug，提到 “red-green-refactor”，希望使用集成测试，或询问“test-first development（先写测试）”。
Ubiquitous Language
ProgrammerAnthony/Anything-Extract
从当前对话中抽取 DDD 风格的“统一语言”术语表（ubiquitous language glossary），标记歧义，并提出规范的术语选择。保存为 UBIQUITOUSLANGUAGE.md。适用于用户希望定义领域术语、构建术语表、固化用词并强化术语一致性，或提到 “domain model” / “DDD”（领域模型与 DDD）。
Write A Skill
ProgrammerAnthony/Anything-Extract
以正确的技能结构、渐进式披露与打包资源来创建新的 agent 技能。适用于用户希望创建、编写或构建新的技能. An agent skill from ProgrammerAnthony/Anything-Extract.
Architecture Doc
ProgrammerAnthony/Anything-Extract
指导在项目中编写、更新与使用架构文档（ARCHITECTURE.md）。在根目录维护架构文档，修改前后需阅读文档；文档关注最终结果与流程串联，不陷入实现细节。适用于新增/变更功能、重构、或需要理解系统整体时。
Related
Works with
Categories
Questions about Frontend Code Review
What does Frontend Code Review do?
指导在项目中对前端代码（Next.js/React/TypeScript/Tailwind 等）进行结构、可维护性、性能与一致性审查，基于既定规则清单。适用于用户请求审查 .tsx/.ts/.js/.jsx 等前端文件或前端目录下的页面与组件。不用于后端代码（如 .py）。. Frontend Code Review is an agent skill from ProgrammerAnthony/Anything-Extract.
When should I use Frontend Code Review?
Frontend Code Review fits situations like: tasks that involve React components; tasks that involve CSS and styling; tasks that involve Code review.
How do I install Frontend Code Review in Claude Code?
Run `npx skills add ProgrammerAnthony/Anything-Extract --skill frontend-code-review -a claude-code`. Or copy the skill folder (.agents/skills/frontend-code-review in ProgrammerAnthony/Anything-Extract) into .claude/skills/frontend-code-review in your project. Claude Code loads it when a task matches its description.
How do I install Frontend Code Review in Codex?
Run `npx skills add ProgrammerAnthony/Anything-Extract --skill frontend-code-review -a codex`. Or copy the skill folder (.agents/skills/frontend-code-review in ProgrammerAnthony/Anything-Extract) into .agents/skills/frontend-code-review in your project. Codex loads it when a task matches its description.
Can I use Frontend Code Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ProgrammerAnthony/Anything-Extract --skill frontend-code-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/frontend-code-review, .gemini/skills/frontend-code-review, .github/skills/frontend-code-review and .opencode/skills/frontend-code-review in your project.
What does Frontend Code Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Frontend Code Review is instructions for the agent only.
Does Frontend Code Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Frontend Code Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Frontend Code Review use?
Frontend Code Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Frontend Code Review use?
About 957 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.7k tokens, read only when the agent opens those files.
What are the alternatives to Frontend Code Review?
Skills that share tags, products or a category with Frontend Code Review: Frontend Code Review (ProgrammerAnthony/Expert-Coding-Harness, 235 stars), Bmm Iconify Icons (Y80/bmm, 343 stars), Shadcn Tailwind UI (LiarMTTT/TavernWeave, 148 stars) and Dokan Frontend Dev (getdokan/dokan, 288 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Frontend Code Review?
ProgrammerAnthony (a GitHub user) maintains it in ProgrammerAnthony/Anything-Extract, which has 139 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on May 13, 2026.
Source: ProgrammerAnthony/Anything-Extract on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.