Suede AI Skills Directory

setup-pre-commit vs test-driven-development

A comparison selected for Test Automation. Compare the task description and license first, then use the score breakdown to inspect their published files.

Quality snapshot: 2026-10-22. Install counts: skills.sh, 2026-11-08. This pair was selected from shared topics and recorded installs; it is not a claim about joint search volume.

At a glance

Evidencesetup-pre-commit (mattpocock/skills)test-driven-development (obra/superpowers)
Listingsetup-pre-committest-driven-development
TaskSet up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.Use when implementing any feature or bugfix, before writing implementation code
Quality score75/100 · C80/100 · B
LicenseMITMIT
Cost lanefree-open-sourcefree-open-source
Recorded installs532,683272,959
ReportScore reportScore report

Where the scores differ

Componentsetup-pre-committest-driven-development
Structural checks56 / 5656 / 56
Description length5 / 51 / 5
Boundary clause0 / 40 / 4
Example request0 / 30 / 3
Instruction depth4 / 77 / 7
Reference files0 / 30 / 3
Bundled scripts0 / 20 / 2
Recent maintenance9 / 99 / 9
Curated-list citations1 / 77 / 7
Tool permissions declared0 / 20 / 2
Compatibility declared0 / 20 / 2

test-driven-development has the higher structural-quality score by 5 points. Use the task descriptions above to judge fit. These scores do not measure runtime performance or security.

Inspect before installing

setup-pre-commit and test-driven-development link to their publishers, licenses and installation routes. Read the source before giving either skill access to your project.