Frontend Reviewer
Review frontend code, UI changes, generated implementations, and pull requests with severity-based findings and checklist-driven analysis. Use when auditing React/TypeScript/CSS code, validating AI-generated frontend output, performing acceptance review before merge, or checking whether a frontend change is safe to ship.
Install
$ agentstack add skill-ceilf6-frontagent-frontend-reviewer ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ceilf6-frontagent-frontend-reviewer) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Frontend Reviewer
Review relevant frontend files and produce concrete findings ordered by severity. Keep the review evidence-based, concise, and actionable.
Workflow
- Read
references/severity-rubric.md. - Read
references/review-checklist.md. - Read
references/frontend-quality-rules.mdwhen architecture, layering, or maintainability questions matter. - Inspect only the files relevant to the request, the diff, or the changed surfaces implied by the task.
- Report findings grouped by severity, highest risk first.
- If no findings exist, state that explicitly and mention residual risks or testing gaps.
Output Contract
- Start with findings. Do not lead with a summary.
- For each finding include:
- affected file path
- optional line number when known
- severity
- why it matters
- shortest viable fix direction
- Prefer one issue per finding. Split unrelated problems.
- Use exact evidence. Avoid generic advice.
Guardrails
- Do not invent files, line numbers, or user intent.
- Do not upgrade style nits into blocking issues.
- Do not hide uncertainty. Mark assumptions when evidence is incomplete.
- Do not spend space on praise unless the user explicitly asks for it.
- Prefer behavioral regressions, data-flow bugs, accessibility issues, and missing tests over cosmetic commentary.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ceilf6
- Source: ceilf6/FrontAgent
- License: MIT
- Homepage: https://marketplace.visualstudio.com/items?itemName=ceilf6.frontagent
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.