Skills frontend-review

📦

frontend-review

Name: frontend-review
Author: yaojingang

Content revision r1 Safe ⚙️ External commands

Review Frontend Code Before Merge

Frontend reviews often miss accessibility gaps, unsafe rendering paths, and incomplete UI states. This skill gives Claude, Codex, or Claude Code a focused review checklist for practical pre-merge feedback.

Supports: Claude Codex Code(CC)

📊 75 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "frontend-review" from https://skillstore.io/skills/yaojingang-frontend-review.md and its manifest at https://skillstore.io/api/skills/yaojingang-frontend-review/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/yaojingang-frontend-review.md Signed manifest GET /api/skills/yaojingang-frontend-review/manifest Signed lockfile GET /api/skills/yaojingang-frontend-review/lockfile

Test it

Using "frontend-review". Review a new modal component before merge.

Expected outcome:

Finding: The dialog opens without moving focus into the modal.
Impact: Keyboard users may continue interacting with background controls.
Fix: Move focus to the dialog title or first actionable control when opened.

Using "frontend-review". Review a search results page with async loading.

Expected outcome:

Finding: The empty state and error state are not distinct.
Impact: Users cannot tell whether no results exist or the request failed.
Fix: Add separate empty, loading, and retryable error states.

Using "frontend-review". Review a component that renders user-provided content.

Expected outcome:

Finding: Confirm whether rendered content is sanitized before display.
Impact: Untrusted markup can become a cross-site scripting risk.
Fix: Use safe rendering defaults and document any trusted HTML boundary.

Security Audit

Safe

v4 • 7/8/2026 Open versioned report

The single static finding is a false positive. SKILL.md line 26 uses Markdown backticks to format a local checklist path, not to execute shell or Ruby commands. No prompt injection or malicious intent was found in the reviewed files.

Files scanned

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (1)

SKILL.md:26

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/yaojingang-frontend-review/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/yaojingang-frontend-review/security.svg)](https://skillstore.io/skills/yaojingang-frontend-review?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/yaojingang-frontend-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/yaojingang-frontend-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/yaojingang-frontend-review.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

yaojingang. (2026). frontend-review security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/yaojingang-frontend-review/audits/4

BibTeX citation

@techreport{yaojingang-yaojingang-frontend-review-2026,
  author = {yaojingang},
  title = {frontend-review security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/yaojingang-frontend-review/audits/4},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "frontend-review security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
  - name: "yaojingang"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/yaojingang-frontend-review/audits/4"
identifiers:
  - type: other
    value: "skillstore:yaojingang-frontend-review:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Pre-Merge React Review

Review a pull request for accessibility, unsafe rendering, and missing user states before approval.

Design System Component Check

Assess shared components for keyboard behavior, focus management, disabled states, and consistent error handling.

Security-Aware UI Review

Find UI paths that render untrusted content or handle forms without clear validation and recovery states.

Try These Prompts

Basic Component Review

Use frontend-review to review this component for accessibility, unsafe rendering, and missing loading or error states.

Pull Request Review

Use frontend-review on this frontend change. Prioritize findings by severity and include concrete file references.

Form Flow Review

Use frontend-review to inspect this form flow for validation gaps, pending states, disabled states, focus handling, and error recovery.

Security and Accessibility Review

Use frontend-review for a strict review of unsafe rendering, dangerous HTML injection paths, keyboard navigation, focus behavior, and residual test gaps.

Best Practices

Provide the changed files, related components, and expected user flow.
Ask for findings first, then open questions and test gaps.
Include product requirements when accessibility or state behavior depends on intent.