Expert husky capability pack for lightweight local quality gates, commit message enforcement, and low-friction contributor workflows.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
3 prerequisites to line up before setup.
Safety & privacy surface
1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens, network access.
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
# 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 checklistThis capability pack is pinned to documentation verified on 2026-04-11.
This skill focuses on practical local governance: catch avoidable issues early while preserving fast contributor loops.
SKILL.md.SKILL.md content as reusable workflow instructions..gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported..cursor/rules/*.mdc adapter for project rules.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.
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.
[](https://heyclau.de/entry/skills/husky-commit-governance-capability-pack)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 status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2026-04-11 | Package verified2026-04-11 | Package not verified |
| Source provenanceDiffers | Source-backed | No submission link | Submission linkedSource submission |
| SubmitterDiffers | — | — | kiannidev |
| Install risk | Review first | Low risk | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — |
| Category | skills | skills | skills |
| Source | First-party | First-party | Source-backed |
| Author | JSONbored | JSONbored | kiannidev |
| Added | 2026-04-11 | 2026-04-11 | 2026-06-15 |
| Platforms | |||
| Harness | |||
| Source repo | — | — | — |
| 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. | ✓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 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. | ✓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 |
|
|
|
| Install | | | — |
| Config | — | — | — |
| Citations | |||
| Claim | Unclaimed | Unclaimed | Unclaimed |
Generate stable, high-signal changelogs and release notes with git-cliff and conventional commit discipline.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.