Repo brief: sds/overcommit

Generated by RepoPilot · document generated 2026-09-13 · concise human review Evidence snapshot · analyzed 2026-09-13T11:31:58.899Z · commit 9c58008c1906

Verdict

Healthy — Strong maintenance signals

• Last commit 6w ago
• 34+ active contributors
• MIT licensed
• CI configured
• 1 more receipt on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

Overcommit is a Git hook manager written in Ruby that installs, configures, and runs Git hooks (pre-commit, commit-msg, post-checkout, etc.) with built-in and custom rule validation. It replaces manual .git/hooks scripting with a declarative YAML configuration (.overcommit.yml) and provides 50+ pre-built hooks for linting, dependency management, and commit message validation across teams. Single-package Ruby gem organized as: lib/overcommit/ contains the core engine (CLI, configuration loader, git repo wrapper), lib/overcommit/hook/ subdivides into type-specific hooks (commit_msg/, pre_commit/, post_checkout/, etc.), each with base.rb + concrete implementations. Config lives in…

Start here

Open these first:

• lib/overcommit.rb — Main entry point and gem loader; initializes the entire Overcommit system.
• lib/overcommit/cli.rb — Command-line interface parser and orchestrator; routes all user commands to appropriate handlers.
• lib/overcommit/hook/base.rb — Abstract base class for all hooks; defines the core hook execution and result handling contract.
• lib/overcommit/configuration_loader.rb — Loads and parses YAML configuration files; critical for understanding hook setup and user customization.
• lib/overcommit/git_repo.rb — Git repository abstraction; manages interaction with Git and hooks installation/removal.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

git clone https://github.com/sds/overcommit.git && cd overcommit && bundle install && bundle exec bin/overcommit --install. Then edit .overcommit.yml to enable/disable hooks, or run bundle exec bin/overcommit --run to t…

Daily commands:

bundle exec bin/overcommit --install (installs hooks into .git/hooks/), then git commit (hooks run automatically). For testing: bundle exec bin/overcommit --run [hook_type]. For CI: SKIP_OVERCOMMIT=1 disables hooks, or…

…shortened for this brief.

Key cautions & unknowns

• Concentrated ownership — top contributor handles 52% of recent commits
• 1. Hook execution happens in git/.hooks/ generated scripts (not in version control) — changes to .overcommit.yml require re-running --install. 2. OVERCOMMIT_SKIP=1 env var disables ALL hooks; understand this is a full…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.