check-frontend

Verify frontend code changes against repository guidelines and report violations.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Lin117-shygo/ros_car --skill check-frontend-lin117-shygo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-frontend
Source: https://github.com/Lin117-shygo/ros_car/tree/main/.agents/skills/check-frontend
Command: npx skills add https://github.com/Lin117-shygo/ros_car --skill check-frontend-lin117-shygo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify that your latest frontend changes conform to established frontend development guidelines, reducing rework and regressions.

Core Features & Use Cases

  • Read the official frontend guidelines from the repository and determine which rules apply to your changes.
  • Analyze code diffs to identify violations across components, hooks, state management, and type safety.
  • Provide actionable feedback and suggested fixes to quickly align code with best practices.

Quick Start

Run this skill after you finish coding to verify your changes against the frontend guidelines.

Frequently Asked Questions about check-frontend

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

FAQPage Schema
How do I check frontend code against best practices during a code review?

To check frontend code against best practices, run this Skill to verify your code diffs. It reads established guidelines from your repository and reports violations across components, hooks, state, and types.

What is the best way to ensure frontend code consistency before merging changes?

The best way to ensure frontend code consistency is to validate your latest changes against official guidelines. This Skill analyzes code diffs to identify violations and provides actionable feedback with suggested fixes to reduce rework.

Does this frontend code review tool require specific guideline files in the repository?

Yes, this frontend code review tool requires specific guideline files. It needs to read the `.trellis/spec/frontend/index.md` file and the relevant guideline files within your repository to evaluate compliance accurately.

When do I need to run a frontend guidelines check on my project?

You need to run a frontend guidelines check during development and code review when your changes touch components, hooks, state, or types. Running it after you finish coding verifies compliance and prevents regressions.

Can I get suggested fixes for frontend state and hook violations found in the diff?

Yes, you can get suggested fixes for frontend state and hook violations. The Skill analyzes your code diff, evaluates compliance against the guidelines, and provides actionable feedback to quickly align your code.