fe-lead

Identify and report high-severity frontend issues during code reviews.

1|Updated Mar 24, 2026

Search Tags:#architecture #performance #security #frontend #code-review #pr-review

Ready to run

npx skills add https://github.com/gridi-ai/gridi-skills --skill fe-lead

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fe-lead
Source: https://github.com/gridi-ai/gridi-skills/tree/main/skills/fe-lead
Command: npx skills add https://github.com/gridi-ai/gridi-skills --skill fe-lead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend code reviews can be noisy and inconsistent; this skill analyzes PRs or code changes to report only high-severity issues such as bugs, performance problems, security vulnerabilities, and architecture violations.

Core Features & Use Cases

Focused frontend reviews that surface critical issues with minimal noise.
Works on PRs, changed files, or FE review requests to guide fixes and improve code quality.
Use Case: When reviewing a PR, identify high-impact defects and architectural misalignments to accelerate shipping with confidence.

Quick Start

Submit a GitHub PR URL or a path to the frontend code you want reviewed.

Frequently Asked Questions about fe-lead

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

FAQPage Schema

How do I find high-severity frontend issues during a PR review?▼

To find high-severity frontend issues during a PR review, analyze code changes to surface bugs, performance bottlenecks, security vulnerabilities, and architecture violations while filtering out low-impact noise. This enforces context gathering and architecture adherence checks to produce a structured verdict.

Can I use automated frontend code review to check performance and accessibility?▼

Yes, automated frontend code review can check performance and accessibility. It enforces specific workflow steps including context gathering, architecture adherence, performance considerations, and accessibility checks to identify critical defects across diverse frontend stacks.

What is the best way to review changed frontend files for security vulnerabilities?▼

The best way to review changed frontend files for security vulnerabilities is to apply a structured analysis that reports only high-severity issues. This approach enforces security checks and produces a concise report with severity labels to guide necessary fixes.

Does this frontend review approach work with diverse frontend stacks?▼

Yes, this frontend review approach works with diverse frontend stacks. It applies to PR reviews, changed file analyses, and FE review requests across various technologies to surface architecture violations and high-impact defects.

How do I get a structured verdict with severity labels for frontend code changes?▼

To get a structured verdict with severity labels for frontend code changes, apply an advanced review process that evaluates performance, security, and architecture. It produces a concise report highlighting only high-severity issues to accelerate shipping with confidence.