CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/git-hooks-automation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%Scale 1-5

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

This is a highly actionable and comprehensive skill with excellent executable examples covering multiple ecosystems (Node/Husky, Python/pre-commit, custom shell). Its main weakness is verbosity — it explains fundamentals Claude already knows (what git hooks are, the hook types table) and packs too much content into a single file rather than using progressive disclosure. The workflow sequencing is solid but could benefit from explicit verification steps after setup.

Suggestions

Remove or drastically shorten the 'Git Hooks Fundamentals' section — Claude knows what git hooks are and when they fire. Keep only the hook types table if it serves as a quick reference.

Remove the 'When to Use This Skill' section entirely — this is routing metadata that belongs in frontmatter, not body content.

Split the content into separate files: keep Husky quick setup and pre-commit quick setup in SKILL.md, move custom hooks, CI integration, migration guide, and troubleshooting to referenced bundle files.

Add an explicit verification step after each setup workflow, e.g., 'Test: make a small change, stage it, and commit to verify hooks fire correctly.'

DimensionReasoningScore

Conciseness

The skill is comprehensive but noticeably verbose at ~350 lines. The 'Git Hooks Fundamentals' section explaining what hooks are and the full hook types table is information Claude already knows. The 'When to Use This Skill' section is also padding. However, the code examples themselves are tight and the pitfalls/migration sections add genuine value.

3 / 5

Actionability

Excellent actionability throughout — every section provides copy-paste ready commands and config files. The Husky setup, lint-staged config, pre-commit framework YAML, custom shell hooks, and CI integration are all fully executable with no pseudocode or vague instructions.

5 / 5

Workflow Clarity

The Husky setup follows a clear sequence (install → init → configure lint-staged → add commit-msg hook → add pre-push). The migration guide and gradual adoption sections are well-sequenced. However, there's no explicit validation/verification step after setup (e.g., 'run a test commit to verify hooks fire correctly'), which is a minor gap. Since this isn't a destructive/batch operation, the missing validation doesn't cap the score.

4 / 5

Progressive Disclosure

The content is a monolithic file with no bundle files to offload detail into. The pre-commit framework config, custom hook scripts, CI integration, migration guide, and troubleshooting could all be separate referenced files. The 'Related Skills' section references other skills but the main content itself would benefit from splitting. For a skill this long (~350 lines), inlining everything is suboptimal.

3 / 5

Total

15

/

20

Passed

Description

70%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.

The description is strong in specificity and distinctiveness, naming concrete tools and actions that clearly define its niche. However, it lacks an explicit 'Use when...' clause, which weakens its completeness for skill selection purposes. Adding trigger guidance would significantly improve Claude's ability to select this skill at the right time.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about setting up Git hooks, configuring Husky, enforcing commit conventions, or adding pre-commit checks'

Include additional natural trigger terms like 'conventional commits', 'pre-push hooks', or '.husky configuration' to capture more user phrasings

DimensionReasoningScore

Specificity

Lists several specific actions and tools: Git hooks setup with Husky, lint-staged, pre-commit framework, commitlint, code quality gates, formatting, linting, and commit message enforcement. Minor gaps in coverage (e.g., doesn't mention specific configuration steps or file types).

4 / 5

Completeness

Has a clear 'what' (setup Git hooks with specific tools, automate quality gates) but no explicit 'when' clause. The description lacks a 'Use when...' trigger guidance, which caps this at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: 'Git hooks', 'Husky', 'lint-staged', 'pre-commit', 'commitlint', 'linting', 'formatting', 'commit message'. Missing some variations like 'pre-push', 'githooks', '.husky', or 'conventional commits'.

4 / 5

Distinctiveness Conflict Risk

Very clear niche focused specifically on Git hooks tooling (Husky, lint-staged, pre-commit, commitlint). Unlikely to conflict with general linting skills or CI/CD skills due to the specific hook-based automation focus.

5 / 5

Total

16

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.