skills.rest
MaShouo
MaShouoCOMMUNITY
Explore all skills by this author →
GitHub

check-frontend

Identify frontend guideline violations in recent code changes and report fixes.

Updated Aug 23, 2026
Search Tags:#linting#frontend#quality#web-development#guidelines#code-review
One-click install
npx skills add https://github.com/MaShouo/CodexAuthExchange --skill check-frontend-mashouo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-frontend
Source: https://github.com/MaShouo/CodexAuthExchange/tree/main/.agents/skills/check-frontend
Command: npx skills add https://github.com/MaShouo/CodexAuthExchange --skill check-frontend-mashouo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checklists ensure frontend code changes conform to established frontend guidelines, helping maintain quality and consistency across projects.

Core Features & Use Cases

  • Enforces alignment with frontend guidelines by referencing guideline sources like .trellis/spec/frontend.
  • Guides users to identify and fix violations in component, hook, state, type, and quality areas.
  • Useful for code reviews, PR checks, and automated QA to maintain frontend standards.

Quick Start

Run a quick verification of your recent frontend changes against the guideline references to identify and fix violations.

Frequently Asked Questions about check-frontend

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

FAQPage Schema
How do I check recent frontend code changes against project guidelines?▼

Frontend code review involves identifying deviations from guidelines in recent changes by evaluating components, hooks, state, and types against specified files, then returning a structured report detailing violations and suggested fixes.

How do I automate frontend code review for PR checks?▼

Automating frontend code review for PR checks requires applying specified guideline files to evaluate recent code changes, generating a structured report that highlights violations and provides references to exact guideline sources for fixes.

What is the process for identifying frontend guideline violations in web development?▼

Identifying frontend guideline violations in web development involves scanning recent code changes for deviations in component, hook, state, type, and quality areas, referencing established guideline files to produce a structured violation report.

Does frontend code linting work with custom specification files?▼

Yes, frontend code linting works with custom specification files by directly applying the guidelines specified in your project's spec files to evaluate recent changes and return detailed violation reports with exact references.

What's the best way to enforce frontend quality and consistency standards?▼

The best way to enforce frontend quality and consistency standards is to evaluate recent code changes against established project guidelines, specifically checking component, hook, state, and type modifications for violations.

Why are my frontend components failing code review despite passing local linting?▼

Frontend components may fail code review if local linting does not check against specific project guidelines, whereas a dedicated review process evaluates component, hook, state, and type changes against exact spec files to find violations.

Related Skills

Explore More Software Engineering Skills→
WanxiaJaneYangWanxiaJaneYang

before-frontend-dev

Direct users to frontend development guidelines in `.trellis/spec/frontend/index.md` before coding.

Community
Basic
lucascarolucascaro

gc-sweep

Detect and correct code deviations against golden-principle guidelines in repositories.

Community
Intermediate
michaelsvanbeekmichaelsvanbeek
1

code-review

Automate pull request code reviews with standardized linting, testing, security, and CI/CD checks.

Community
Advanced
unclehowellunclehowell

subagent-driven-development

Execute implementation plans by dispatching fresh subagents for each task.

Community
Advanced