Git Commit Hooks

🚀Git Commit Hooks

Active

Keep repository checks active when Custy runs locally or inside a different operating-system container.

Command[tool.custy.git.hooks]

📦Category

Git Configuration

🚀Quick Command

[tool.custy.git.hooks]

---

safe defaultspre-commitcontainers

---

📋

Property

mode

⚙️

Default

auto

✅

Silent Bypass

Never

🌿

No-Hook Projects

Native Git

Configuration

📋Properties

Property	Type	Description	Default	Required
mode	auto | native | pre_commit	Select native Git execution or verified direct pre-commit execution.	auto	No

Recommended default

toml

[tool.custy.git.hooks]
mode = "auto"

Behavior Matrix

ℹ️Hook Resolution

auto + no installed hook	Use normal Git commit behavior. pre-commit is not required or activated.
auto + compatible hook	Let Git execute the installed hook natively.
auto + incompatible pre-commit wrapper	Run the recognized configured pre-commit stage directly, then skip only that already-completed wrapper for the current commit.
auto + incompatible custom hook	Stop safely because Custy cannot prove an equivalent execution path.
native	Always let Git execute installed hooks exactly as stored in the repository.
pre_commit	Require .pre-commit-config.yaml and the pre-commit executable, run configured stages directly, and continue only after they pass.

ℹ️A configuration file alone does not install a hook

In auto mode, .pre-commit-config.yaml without an installed .git/hooks/pre-commit wrapper behaves like a normal no-hook repository. Use pre-commit install when the project intends Git to enforce those checks, or choose pre_commit explicitly when Custy should require direct execution.

⚠️Direct execution is validation, not a bypass

Custy uses Git's --no-verify only after every recognized wrapper that flag would bypass has completed successfully through pre-commit. Unknown custom hooks, unavailable tooling, missing configuration, and failed checks stop the workflow. There is no skip mode.

Local and Docker Guidance

• Keep mode = "auto" for most projects, including projects that do not use pre-commit.
• Use native when custom hooks are already portable across every execution environment.
• Use pre_commit when project policy requires direct framework execution.
• Install local support with pip install "custy[hooks]". The production image already contains pre-commit.
• A failing direct check returns PRE_COMMIT_HOOK_FAILED and does not create a Git commit.

Continue

🚀Related Commands

Commands commonly used together with this command.

Git Overview

Navigate remotes, push strategy, and hooks.

Docker

Run Custy against mounted repositories.

Commit Troubleshooting

Resolve hook and commit failures.