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.

62

Quality

74%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/git-hooks-automation/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is highly actionable with comprehensive executable examples and clear sequenced workflows, held back only slightly by minor verbosity and the lack of any progressive-disclosure split into reference files.

Suggestions

Add an explicit validation step to the setup and migration workflows, e.g. 'Verify: make a throwaway commit and confirm the hook fires.'

Trim the 'Git Hooks Fundamentals' intro and the 'Key Principles' list, which restate guidance already shown in the code.

Consider moving the CI Integration and Migration Guide sections into reference files to keep SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly executable code and commands with little padding, though the 'Git Hooks Fundamentals' prose and the 'Key Principles' restatement add minor over-explanation that could be trimmed.

4 / 5

Actionability

Fully executable, copy-paste-ready configs and scripts for Husky/lint-staged, commitlint, the pre-commit framework, custom shell hooks, and CI workflows, covering the common cases.

5 / 5

Workflow Clarity

Setup, migration (v4→v9), and adoption flows are clearly numbered and sequenced; minor gap is the absence of an explicit 'verify the hook fires' checkpoint, but this is config setup rather than a destructive/batch operation so the 3-cap does not apply.

4 / 5

Progressive Disclosure

No bundle files exist, so scoring reflects organization; the body is well-sectioned with clear headers, though the CI integration, migration guide, and custom hook scripts could plausibly be split into one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

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

The description is specific and well-targeted with strong natural trigger terms, but it lacks an explicit 'Use when...' clause, leaving the 'when' only weakly implied and capping completeness at 3.

Suggestions

Add an explicit 'Use when...' sentence, e.g. 'Use when setting up or migrating Git hooks, or when the user mentions Husky, lint-staged, pre-commit, or commitlint.'

Drop the filler verb 'Master' to tighten the opening and lead with the concrete action.

Include common synonyms like 'githooks' and 'Conventional Commits' to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (setup, automate formatting/linting, commit message enforcement) alongside named tools; not quite comprehensive enough for a 5 given 'Master' is mild fluff and coverage is tool-name-heavy.

4 / 5

Completeness

Clear 'what' (set up hooks with named tools to automate quality gates) but no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

Strong natural keywords users actually say ('Git hooks', 'Husky', 'lint-staged', 'pre-commit', 'commitlint', 'CI'), but a few common synonyms (githooks, Conventional Commits) are missing.

4 / 5

Distinctiveness Conflict Risk

The named toolchain (Husky, lint-staged, pre-commit, commitlint) carves a clear niche with minimal overlap; not a 5 because the missing 'Use when' clause weakens trigger distinctiveness.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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