Skip to main content
skillsFirst-partyReview first Safety Privacy

Husky Commit Governance Capability Pack Skill

Expert husky capability pack for lightweight local quality gates, commit message enforcement, and low-friction contributor workflows.

HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:expertType:capability-packVerified:validated
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://typicode.github.io/husky/, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/husky-commit-governance-capability-pack.mdx
Package URL
/downloads/skills/husky-commit-governance-capability-pack.zip
Package SHA256
aef3f6a1d69042ef5f12ff5dc7958397dd7c5de9bbbcf55d4b7211f0e0eef66b
Safety notes
Installs from a downloaded package and may run local commands or scaffold files as part of the workflow; review the package and any generated changes before applying.
Privacy notes
Operates on your local project files and any context you share in the session; review what you expose before sharing — nothing is sent beyond the model unless a step calls an external service.
Platform compatibility
claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
Author
JSONbored
Claim status
unclaimed
Last verified
2026-04-11

Decision playbook

Ready to evaluate for your workflow

Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.

Compare context
Selected

0

Current score

96

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Complete

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as first-party.

    Done
  • Metadata reviewed

    Registry metadata indicates a reviewed listing.

    Done

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Complete

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    Package marked verified.

    Done
  • Checksum metadata

    SHA-256 hash is present.

    Done

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

Package install

Copy-ready — paste the snippet to get started.

Install command

Provided

Config snippet

Not provided

Copy snippet

Provided

Prerequisites

3 to clear

Platforms

6 listed

Difficulty

79/100

Adoption plan

Balanced adoption plan

Current risk score 0/100. Use staged verification before broader rollout.

Risk 0

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    Package verification/checksum metadata is available.

    Done

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (6/6 signals complete).

Risk 0

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Present

Package integrity metadata is present.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

6/6 steps complete with no blocking gaps for this preset.

Risk 0

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is available.

Done

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

3 prerequisites to line up before setup.

0/3 ready
General3

Safety & privacy surface

Safety & privacy surface

1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens, network access.

2 areas
  • SafetyNetwork accessInstalls from a downloaded package and may run local commands or scaffold files as part of the workflow; review the package and any generated changes before applying.
  • PrivacyCredentials & tokensOperates on your local project files and any context you share in the session; review what you expose before sharing — nothing is sent beyond the model unless a step calls an external service.

Safety notes

  • Installs from a downloaded package and may run local commands or scaffold files as part of the workflow; review the package and any generated changes before applying.

Privacy notes

  • Operates on your local project files and any context you share in the session; review what you expose before sharing — nothing is sent beyond the model unless a step calls an external service.

Prerequisites

  • Node package scripts for validation
  • Conventional commit policy
  • Contributor onboarding docs

Schema details

Install type
package
Reading time
8 min
Difficulty score
79
Troubleshooting
Yes
Breaking changes
No
Package metadata
Package verified
Yes
SHA-256
aef3f6a1d69042ef5f12ff5dc7958397dd7c5de9bbbcf55d4b7211f0e0eef66b
Skill and platform metadata
Skill type
capability-pack
Skill level
expert
Verification
validated
Verified at
2026-04-11
Retrieval sources
https://typicode.github.io/husky/https://www.conventionalcommits.org/en/v1.0.0/https://commitlint.js.org/
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
PlatformSupportInstall path
claude-codeNative.claude/skills/<skill-name>/SKILL.md
codexNative.agents/skills/<skill-name>/SKILL.md
windsurfNative.windsurf/skills/<skill-name>/SKILL.md
geminiNative.gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md
cursorAdapter.cursor/rules/<skill-name>.mdc
cliManualAGENTS.md or tool-specific context file
Full copyable content
# Trigger
"Apply the husky commit governance capability pack to this repository."

# Required output
1) Hook matrix (pre-commit, commit-msg, optional pre-push)
2) Fast-path command list (< 10s target)
3) Contributor bypass/override policy
4) Drift and maintenance checklist

About this resource

Knowledge Freshness

This capability pack is pinned to documentation verified on 2026-04-11.

Retrieval Sources

Core Workflow

  1. Define minimum local gate set for the repository type.
  2. Keep hooks fast and deterministic to avoid bypass behavior.
  3. Enforce commit message standard with clear error messages.
  4. Align local checks with CI checks to prevent drift.
  5. Document safe bypass conditions for emergency workflows.

Overview

This skill focuses on practical local governance: catch avoidable issues early while preserving fast contributor loops.

Capability Scope

  • Hook design and prioritization
  • Runtime/latency optimization
  • Commit message policy enforcement
  • Contributor ergonomics and onboarding
  • Governance drift controls

Compatibility

Native

  • Claude Code / Claude: native skill usage via SKILL.md.
  • Codex/OpenAI workflows: compatible with Agent Skills-style SKILL.md content as reusable workflow instructions.

Manual Adaptation

  • Gemini CLI: native skill usage via .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported.
  • Cursor: use the generated .cursor/rules/*.mdc adapter for project rules.
  • OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.

Production Rules

  • Keep pre-commit checks fast enough to avoid bypass patterns.
  • Use the same underlying scripts for local hooks and CI.
  • Document approved bypass conditions for emergency fixes only.
  • Treat commit-msg enforcement as required for changelog quality.

Troubleshooting

Issue: Hooks are too slow and developers bypass them
Fix: keep pre-commit to staged-file checks only.

Issue: Hook failures differ from CI failures
Fix: use shared scripts for local and CI paths.

Issue: Commit message confusion
Fix: provide examples in failing output and contributor docs.

Output Contract

  1. Minimal hook policy with justifications.
  2. Exact script wiring in package manager config.
  3. Failure UX recommendations.
  4. Maintenance checklist for future contributors.

Source citations

Add this badge to your README

Show that Husky Commit Governance Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/skills/husky-commit-governance-capability-pack.svg)](https://heyclau.de/entry/skills/husky-commit-governance-capability-pack)

How it compares

Husky Commit Governance Capability Pack Skill side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.

Field

Expert husky capability pack for lightweight local quality gates, commit message enforcement, and low-friction contributor workflows.

Open dossier

Expert release-changelog capability pack for git-cliff with conventional commits, deterministic release notes, and low-maintenance versioning.

Open dossier

Expert release changelog generation capability pack for drafting, validating, and publishing user-facing release notes from conventional commits, tags, and GitHub Releases with source-backed review matrices and privacy-safe output.

Open dossier
Next stepsDiffers
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustDiffersPackage verified2026-04-11Package verified2026-04-11Package not verified
Source provenanceDiffersSource-backedNo submission linkSubmission linkedSource submission
SubmitterDifferskiannidev
Install riskReview firstLow riskReview first
Notes Safety Privacy Safety Privacy Safety Privacy
Brand
Categoryskillsskillsskills
Sourcefirst-partyfirst-partysource-backed
AuthorJSONboredJSONboredkiannidev
Added2026-04-112026-04-112026-06-15
Platforms
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Claude CodeCodexWindsurfGeminiCursorCLI
Source repo
Safety notesInstalls from a downloaded package and may run local commands or scaffold files as part of the workflow; review the package and any generated changes before applying.May produce commands or configuration for live infrastructure, CI, releases, or indexing; test changes in staging or dry-run mode first. Use least-privilege API tokens and review workflow, deploy, DNS, cache, and release changes before applying them to production.This skill plans release publication; it must not create tags, publish releases, or push version bumps without explicit maintainer approval. Security and breaking-change entries can affect downstream consumers; require owner review before public release. Automated changelog tools may include contributor handles or internal ticket IDs; scrub before publishing. Do not run release scripts or CI publish workflows from unreviewed fork contexts.
Privacy notesOperates on your local project files and any context you share in the session; review what you expose before sharing — nothing is sent beyond the model unless a step calls an external service.Inputs can include repository metadata, workflow logs, deployment settings, domain names, analytics exports, and service configuration. Redact tokens, account IDs, private URLs, customer data, and proprietary deployment details before sharing generated reports or prompts.Changelog drafts may expose unreleased features, customer names, internal URLs, and security fix details. GitHub compare views and release automation logs can include private repository metadata. Redact embargoed vulnerability details and internal-only migration notes from public release text. Keep registry tokens, npm credentials, and signing keys out of prompts and generated notes.
Prerequisites
  • Node package scripts for validation
  • Conventional commit policy
  • Contributor onboarding docs
  • Conventional commit policy
  • Git tags access
  • Release workflow ownership
  • Access to merged commit history, tags, and release branch or main since the last release.
  • Project changelog policy (keep-a-changelog sections, semver rules, and pre-release handling).
  • Permission to draft release notes without publishing until maintainer approval.
  • GitHub Releases or equivalent publish surface when shipping to users.
Install
curl -L https://heyclau.de/downloads/skills/husky-commit-governance-capability-pack.zip -o husky-commit-governance-capability-pack.zip && unzip -o husky-commit-governance-capability-pack.zip -d ./husky-commit-governance-capability-pack
curl -L https://heyclau.de/downloads/skills/git-cliff-release-changelog-capability-pack.zip -o git-cliff-release-changelog-capability-pack.zip && unzip -o git-cliff-release-changelog-capability-pack.zip -d ./git-cliff-release-changelog-capability-pack
Config
Citations
ClaimUnclaimedUnclaimedUnclaimed
Open 3 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.