22nd of 3 in Code review and testing

front-end-checklist

Front-end rules checklist with an MCP server for agent code review

Stars
74.5k
License
MIT
Last commit
Oct 2026
Last release
May 2026
Language
MDX
Stars, last 29 weeks+2,647
25 Mar 2026: 71,818 stars1 Apr 2026: 71,880 stars8 Apr 2026: 71,927 stars15 Apr 2026: 71,983 stars22 Apr 2026: 72,026 stars29 Apr 2026: 72,078 stars6 May 2026: 72,111 stars13 May 2026: 72,181 stars20 May 2026: 72,227 stars27 May 2026: 72,355 stars3 Jun 2026: 72,453 stars10 Jun 2026: 72,576 stars17 Jun 2026: 72,664 stars24 Jun 2026: 72,745 stars1 Jul 2026: 72,826 stars8 Jul 2026: 72,908 stars15 Jul 2026: 72,987 stars22 Jul 2026: 73,066 stars29 Jul 2026: 73,161 stars5 Aug 2026: 73,262 stars12 Aug 2026: 73,353 stars19 Aug 2026: 73,431 stars26 Aug 2026: 73,769 stars2 Sept 2026: 73,912 stars9 Sept 2026: 73,992 stars16 Sept 2026: 74,086 stars23 Sept 2026: 74,188 stars30 Sept 2026: 74,279 stars7 Oct 2026: 74,371 stars14 Oct 2026: 74,465 stars

71,818 on 25 Mar 202674,465 on 14 Oct 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

A corpus of 386 English front-end rules across 11 categories (HTML, CSS, JavaScript, performance, accessibility, SEO, security, images, testing, privacy, i18n), each with a priority level, remediation guidance and verification steps. It is readable on the website or in the README, and a hosted MCP server and installable skills let agents review code or audit public URLs against the same rules.

Who it is for: Front-end developers and teams auditing sites or feeding rules to agents

Strengths

  • 386 rules with Critical/High/Medium/Low priorities, grouped into 11 categories
  • Hosted MCP server exposes 11 tools, including review_code, search_rules and audit_url
  • Skills install with `npx skills add frontendchecklist/skills`, global or per rule
  • MIT licensed; rules also usable as a plain README checklist without any tooling

Weaknesses

  • Content repo, not a linter: findings come from an agent applying the rules
  • audit_url only handles public https:// pages
  • Security, privacy and i18n categories are thin (22, 5 and 5 rules)
  • MCP tool discovery can be lazy in some clients; the prompt must name the server

What it needs

  • no GPU
  • Needs MCP-compatible client, pnpm (for contributing)

Head to head

Also in Code review and testing

See all 3
Also in Code review and testing
RankProjectScore
1open-code-reviewCLI that reviews Git diffs with an LLM agent and line-level comments47.2k starsApache-2.074 out of 100
3pr-agentLLM pull request reviewer that comments via /review, /describe and /improve13.4k starsMIT59 out of 100