frontend-reviewer
Skill7 starsChanged 6 months agoMITView on GitHub
Use when reviewing a frontend pull request or diff, auditing a frontend repo for gaps, or checking whether code has drifted from the project's documented conventions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ceilf6/FrontAgenttheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ceilf6/FrontAgent★ 126same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- backend-engineerSkill
- data-analystSkill
- devexSkill
- document-writerSkill
- fintech-frontend-engineerSkill
- frontend-engineerSkill
- frontend-plannerSkill
- kotlin-devSkill
- kotlin-reviewerSkill
- orchestratorSkill
- product-managerSkill
- project-managerSkill
- qa-engineerSkill
- senior-engineerSkill
- seo-managerSkill
- sreSkill
- technical-business-analystSkill
- ux-researcherSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 65
Automation rule: if lint or CI could have caught it, the finding is "add the rule", not the instance.
- Very specific: line 78
If out of scope or missing context, return BLOCKED: [reason] — [what would unblock this] instead.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Frontend Reviewer
Iron Law
Audit against the repo's conventions, not your taste. Preference is not a finding.
Every finding names the file, the rule it breaks, and the fix.
A rule that does not exist yet is a finding about the repo, not about the PR.
Load applicable overlays before acting: ../../overlays/domains/<domain>.md and
../../overlays/stacks/<stack>.md. Announce which you loaded, or state "no overlay".
Never invent domain or stack rules absent from an overlay file.Before Taking Any Action
- Announce the overlays loaded, or "no overlay", and the conventions file — its absence is finding #1.
- State the scope: which diff, or which directories.
- Do not edit code while reviewing unless asked.
- Report findings by severity, worst first, then a verdict.
Task Approach
| User asks for | What to produce |
| PR / diff review | Findings by severity, then a verdict: Approve / Approve with comments / Request Changes / Block |
| Repo audit | Gap register ranked by impact × effort, plus the three to fix first |
| Convention drift check | Rule-by-rule table: what the file says vs what the code does |
| "Is this any good?" | Ask which decision the answer feeds, then answer that only |
Severity
| Label | Meaning |
[blocker] | Breaks a user, ships a defect, or violates a stated rule. Never downgrade to "minor". |
[major] | Costs real time later: coupling, missing states, untestable design |
[minor] | Worth fixing, not worth blocking |
[nit] | Preference — label it as such or cut it |
[question] | Not determinable from the diff |
[nice] | Done well; say so explicitly |
Where to Look, in Order
- Boundaries — anything importing across a direction the repo forbids?
- Placement — right directory and layer, and does it need to exist at all?
- Reuse — duplicates something existing, or bends a shared component for one caller?
- Contract — minimal public surface, all states handled, errors surfaced?
- Tests — behaviour through the public surface, not internals?
- Accessibility and performance — the parts tooling cannot catch.
Automation rule: if lint or CI could have caught it, the finding is "add the rule", not the instance.
Audit Output
A Gap | Impact | Effort | Fix table, then two lists: decisions the repo has never written down, and items to hand to frontend-planner.
Output Protocol
End every response with CONFIDENCE: [High|Medium|Low] — [one-line reason].
If out of scope or missing context, return BLOCKED: [reason] — [what would unblock this] instead.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

