Support for HTML Code sniffer

Description

Contributor guide

Tech stack

javascriptnodejs

Domain

toolingdeveloper experience

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

Node.jscheck build configuration knowledgeHTML CodeSniffer basics

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

20

Research direction

The issue requests integrating HTML CodeSniffer into check build as a new checker. First, review check build's documentation on creating custom checkers or plugins. Then, study HTML CodeSniffer's API (available at its GitHub repo) to understand how to run audits and retrieve results. Consider proposing a design in the issue comments before implementing. Relevant files: likely in the 'checkers' or 'plugins' directory of check build.