Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Sloughi review

Free#23 of 26 in Git Hooks Management Tools

A dependency-free Rust crate for sharing commit hooks through Git configuration.

6.0/10Editor score
Sloughi6.0 Visit Sloughi

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Sloughi is a small, dependency-free Rust crate for projects that need to share and install Git hooks. Added as a Cargo build dependency, it uses a build.rs script to create a hooks directory and configure Git's core.hooksPath. On build, it creates a sample pre-commit hook. The intended audience is developers maintaining solo or small Rust repositories that want hook setup kept in the project workflow rather than managed through separate runtime tooling.

Setup centers on the build process. Sloughi supports a custom hooks directory path, environment-variable exclusions that can skip setup in selected environments, and idempotent installation that preserves existing setup. Projects can choose explicit installation errors or have those errors handled silently. This approach keeps the implementation dependency-free and uses Git's existing hook configuration, while requiring maintainers to understand Cargo build dependencies, build.rs behavior, and the repository's selected hooks path.

Sloughi's focus is narrow: the documented hook stage is commit, and its sample hook is pre-commit. Its ecosystem fit is correspondingly centered on Cargo and Git, with configuration sharing and package-manager integration rather than a broad integration catalog. Cargo workspace compatibility is listed as a TODO, which matters for repositories organized around workspaces. Choose Sloughi when a Rust project needs a small, shared commit-hook installation mechanism with customizable paths and no runtime dependencies. Consider another tool when the workflow depends on multiple hook stages, wider platform integrations, or workspace support that is already established.

Sloughi pros and cons

  • Where it wins
    • Installs shared hooks through Rust build.rs and Git core.hooksPath
    • Idempotent setup preserves existing configuration
    • Zero runtime dependencies with customizable hooks directory
  • Where it doesn't
    • Documents only commit-stage hooks
    • Integrations are limited to Cargo and Git
    • Cargo workspace compatibility remains a documented TODO

Sloughi fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update