Name: git-hooks-automation
Rating: 58.4 (1 reviews)
Author: administrakt0r

git-hooks-automation

Master Git hooks setup with Husky, lint-staged, pre-commit framework, and commitlint. Automate code quality gates, formatting, linting, and commit message enforcement before code reaches CI.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/git-hooks-automation/SKILL.md

The canonical home for this skill is git-hooks-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill with comprehensive copy-paste-ready examples across the Git-hooks toolchain. Its weaknesses are missing validation checkpoints in destructive/batch workflows and a lack of progressive disclosure (everything inlined in one long file).

Suggestions

Add explicit validation steps to setup and migration workflows (e.g., after install, run a test commit to confirm the hook fires; after migration, verify hooks are active).

Split large inline blocks — the CI workflow YAML, the full custom pre-commit script, and the hook-types reference — into reference files and link to them from SKILL.md.

Move pinned third-party version numbers to a single autoupdate-able reference or note them as illustrative to reduce staleness overhead.

Dimension	Reasoning	Score
Conciseness	Content is mostly lean code and tables, but includes light filler ("The modern standard for JavaScript/TypeScript projects") and time-sensitive inline version pins (pre-commit-hooks v4.6.0, black 24.4.2, ruff v0.4.4) that will stale, matching anchor 3 rather than 4.	3 / 5
Actionability	Provides abundant copy-paste-ready bash, JSON, and YAML covering Husky setup, lint-staged config, commitlint, the pre-commit framework, custom hooks, CI integration, and migration — fully executable across common cases.	5 / 5
Workflow Clarity	Setup and migration steps are sequenced, but no validation checkpoints (e.g., "verify the hook fires with a test commit") appear, and the destructive migration (rm -rf .husky, npm uninstall) lacks verification, so the destructive-operation cap holds at 3.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers, but no bundle files exist and all content — CI workflow YAML, the full custom hook script, the hook reference table, and the migration guide — is inlined in a single ~410-line file, matching anchor 3.	3 / 5
	Total	14 / 20 Passed

Description

70%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-targeted description that names concrete tools and actions and is clearly distinct from other skills. Its main weakness is the absence of an explicit "Use when…" trigger clause, which caps completeness.

Suggestions

Add an explicit "Use when…" clause listing trigger phrases (e.g., "Use when setting up pre-commit hooks, configuring Husky/lint-staged, or enforcing Conventional Commits with commitlint").

Mention pre-push test running and broader hook types to lift specificity toward comprehensive coverage.

Include natural synonyms like "githooks" to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the tools (Husky, lint-staged, pre-commit, commitlint) and several concrete actions ("code quality gates, formatting, linting, and commit message enforcement"), matching anchor 4; not a 5 because coverage omits pre-push testing and other hook uses.	4 / 5
Completeness	The "what" is explicit and clear, but there is no "Use when…" clause and the "when" is only weakly implied by "before code reaches CI"; the missing explicit trigger guidance caps this at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural user phrases like "Git hooks", "pre-commit", "lint-staged", and "commit message enforcement" that users would say, but lacks synonyms (githooks) and extension tokens needed for anchor 5.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (Git hook toolchain with named frameworks) with distinct triggers, so overlap with other skills and wrong-skill firing risk is minimal.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/git-hooks-automation/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.