← Browse

@majiayu000/husky

B

Generates Husky Git hooks configuration with pre-commit checks. Creates .husky/pre-commit file for running linting, testing, and formatting before commits.

skillclaude

Install

agr install @majiayu000/husky --target claude

Writes 2 files into .claude/skills/, pinned to git-82e47277.

  • .claude/skills/husky/SKILL.md
  • .claude/skills/husky/metadata.json

Document


name: husky description: Generates Husky Git hooks configuration with pre-commit checks. Creates .husky/pre-commit file for running linting, testing, and formatting before commits.

Husky Skill

Purpose

Generate Husky configuration for Git hooks with proper pre-commit checks.

Instructions

Step 1: Initialize Husky (Already Done During npm install)

The prepare script in package.json automatically runs husky during npm install. This creates the .husky/ directory structure.

Step 2: Create Pre-Commit Hook

CRITICAL: After Husky initialization, you MUST create or replace the .husky/pre-commit file with the proper content.

Do NOT rely on auto-generated default - it creates a default hook with just npm test which is insufficient.

Output

Create the file: .husky/pre-commit

Implementation Steps

  1. Create .husky/pre-commit file with this content:
  • Lint to check all code
  • Stylelint to check Vue and SCSS files for style issues
  • Unit tests to ensure code changes don't break tests
  • Lint-staged to auto-fix and format staged files
  1. Make the hook executable

Notes

  • Pre-commit hook ensures code quality before commits are made
  • Husky is initialized automatically via the prepare script
  • The agent MUST create/replace the pre-commit hook file after initialization

Repository README

Describes majiayu000/claude-skill-registry-data as a whole, which may contain artifacts other than this one. Where this artifact had no useful description of its own, its summary was taken from here.

Claude Skill Registry (Data)

This repo contains the archived skill contents (the heavy, browsable skill files).

Canonical layout

  • Category folders at repo root (e.g. development/, documents/, data/, ...)
  • Each skill lives under a category: <category>/<skill>/SKILL.md + <category>/<skill>/metadata.json
  • Case conflicts are resolved with {name}-{owner}-{repo} suffixes (fallback: -{short-hash}).

Archive status

  • Live badges above are sourced from claude-skill-registry-core stats.json.
  • Counts in this README are intentionally dynamic, not hardcoded.
  • If the badges look stale, refresh the core build/index pipeline rather than editing numbers here.

Where the index + site live

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-82e4727795942026-07-31