When should this skill be used?

Use it when reviewing CI coverage, automated checks, or test strategy related to writing unit tests. It focuses on whether a rule is continuously verified, not just documented.

What does the skill focus on?

It focuses on whether front-end rules are continuously verified by unit tests, rather than only being written down somewhere.

Does it write unit tests for me?

The item describes it as a review aid for coverage, automated checks, and test strategy; it does not state that the skill writes tests itself.

Write unit tests

SkillDev tools

Unit-tests is a skill for AI agents that helps review whether front-end rules are continuously verified by unit tests. When an agent is asked to look at CI coverage, automated checks, or test strategy, this skill guides it to focus on whether each rule is actually checked by tests, not just documented.

Available today. Use it from your connected AI after setup.

No other account needed.

Have an agent environment that supports loading skills.

Then ask your AI: use the Write unit tests skill

What your AI can do with it

Review CI coverage related to unit tests
Assess automated checks for front-end rules
Evaluate test strategy for continuous verification
Distinguish rules that are tested from rules that are only documented

Getting started

Have an agent environment that supports loading skills.
Add the unit-tests skill to the agent's available skills.
Ask the agent to review CI coverage, automated checks, or test strategy for a front-end codebase.
The agent applies the skill to check whether rules are continuously verified by unit tests.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/unit-tests/SKILL.md and read by ahel’s review.

Unit tests catch bugs before they reach production, serve as documentation for expected behavior, and give developers confidence to refactor code without breaking functionality.

Quick Reference

Test business logic, utilities, and edge cases
Aim for 80%+ coverage on critical paths
Use descriptive test names that explain behavior
Mock external dependencies, not internal modules
Run tests in CI to catch regressions early

Check

Check if this codebase has unit tests with good coverage for critical functionality.

Fix

Write unit tests for untested functions and components to improve code reliability.

Explain

Explain how unit tests catch bugs early and serve as documentation for expected behavior.

Code Review

Review tests, CI workflows, and enforcement points related to Write unit tests. Flag exact gaps where the rule is not automatically verified or where failures do not block regressions.

For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/en/rules/testing/unit-tests

Signals

GitHub stars: 74k
Forks: 7k
Last commit: Aug 2026

ahel review

K1binfo
installs-packages (in references/rule.md)

Automated review, not a security audit. Ruleset v1+k2.

Questions

When should this skill be used?: Use it when reviewing CI coverage, automated checks, or test strategy related to writing unit tests. It focuses on whether a rule is continuously verified, not just documented.
What does the skill focus on?: It focuses on whether front-end rules are continuously verified by unit tests, rather than only being written down somewhere.
Does it write unit tests for me?: The item describes it as a review aid for coverage, automated checks, and test strategy; it does not state that the skill writes tests itself.

Advanced

Item type: skill
Key: unit-tests-thedaviddias
Source: github.com/thedaviddias/front-end-checklist

github.com/thedaviddias/front-end-checklist

More in Dev tools

teach
Skill · mattpocock ponytail
Skill · dietrichgebert implement
Skill · mattpocock caveman
Skill · juliusbrussee shadcn
Skill · shadcn benchmark
Skill · affaan-m