Chock.sh Build your plugin
Git repositories

AVAILABLE NOW

Guardrails that live in your repository

Install policies into your own repository: committed with the code, enforced at commit and in CI for contributors who run chock sync, and for agents whose hooks are set up.

Pick your policies

What each policy does in a git repository

35

At commit

Chock refuses the commit, locally and in CI.

11

In agent

The agent's hooks check this once chock sync sets them up. If the hook crashes, the action goes through.

25

Advisory

The agent reads the text, and nothing stops a violation.

Each build counts these from the catalog.

How it works

  1. Pick your policies

    Answer three questions, or take a preset. The builder writes one block of commands.

  2. Run the commands in your repo

    They add each policy at a pinned commit and hash, wire the hooks and write files. You commit those files with your code.

  3. Every clone runs one command

    Git never clones hooks, so each person who clones the repository runs chock sync --repo . once.

Install chock first

The commands need chock on your machine. Read the command before you run it.

pipx install chock

The Install page has the details and the other ways to install. →

Every policy, by what it does in a repository

Each name opens the policy's page. This page reads each tier from the catalog. A policy's grade on one agent does not change its tier.

Checks at commit (35)

Checks in the agent (11)

Advisory (25)