convention-check-hd

Name: convention-check-hd
Availability: InStock
Author: kangmomin

Detect React/Next.js frontend convention violations and generate a structured report.

1|1|Updated Apr 9, 2026

Search Tags:#frontend #react #reporting #nextjs #code-quality #lint #convention

Ready to run

npx skills add https://github.com/kangmomin/harness-plugins --skill convention-check-hd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: convention-check-hd
Source: https://github.com/kangmomin/harness-plugins/tree/main/plugins/hyeondongs-harness/skills/convention-check-hd
Command: npx skills add https://github.com/kangmomin/harness-plugins --skill convention-check-hd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend projects often diverge from agreed conventions, leading to bugs, reduced maintainability, and inconsistent code. This skill automatically detects such violations and reports them to the team.

Core Features & Use Cases

Config-driven checks: Reads a project-specific .hyeondong-config.json and plugin-provided defaults, then runs the selected conventions.
Interactive setup: Use --init to choose conventions (default-conventions and project CLAUDE.md) and update the configuration file.
Diagnostics and reporting: Use --doctor for status checks and generate a clear report of violations, including references to bypass rules and traceability.
Comprehensive checks: Validates code structure, imports, and hook usage to ensure adherence to frontend conventions.

Quick Start

Run the skill in the project root with --init to configure conventions, or with --doctor to diagnose status, and otherwise perform the convention checks automatically.

Frequently Asked Questions about convention-check-hd

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

FAQPage Schema

How do I check frontend convention violations in a React or Next.js project?▼

To check frontend convention violations in a React or Next.js project, run the skill in your project root. It reads project configuration and plugin defaults, then evaluates code structure, imports, and hook usage to report violations automatically.

How do I configure frontend lint conventions for my project?▼

To configure frontend lint conventions, run the skill with the --init flag in your project root. This interactively lets you choose between default conventions and project CLAUDE.md rules, then updates your .hyeondong-config.json file accordingly.

Does this convention checker work with Next.js and React projects?▼

Yes, this convention checker works with Next.js and React projects. It applies plugin-provided defaults and project-level CLAUDE.md rules when present, validating frontend code structure, imports, and hook usage against the configured conventions.

What is the best way to generate a report of frontend code quality issues?▼

The best way to generate a report of frontend code quality issues is to run the skill with the --doctor flag. This diagnoses your project status and outputs a clear report of convention violations, including bypass rules and traceability notes.

Why does my frontend convention check report bypass rules and traceability notes?▼

Your frontend convention check report includes bypass rules and traceability notes to provide structured context for each violation. This helps your team understand exactly which code structure, import, or hook usage rule was broken and how to address it.

What do I need to run automated frontend code checks in my repository?▼

To run automated frontend code checks, you need a React or Next.js project with a .hyeondong-config.json file. Running the skill with --init first sets up the selected conventions, allowing subsequent runs to perform checks automatically.