> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scanoss.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Earnie for Developers

> Check your own work before anyone else has to: the CLI, the pre-commit hook, and MCP.

## Check Your Own Work First

The [Earnie CLI](/en/latest/earnie/using-earnie/earnie-cli) runs a scan against a path, your staged changes, or a diff, from your terminal:

```bash theme={null}
earnie scan path [path]
earnie scan staged
earnie scan diff --base origin/main
```

`earnie hook install` adds a native Git pre-commit hook that runs exactly `earnie scan staged --format hook`, reading the Git index rather than the working tree. `earnie mcp setup` connects Claude Code, Cursor, VS Code, or Codex over MCP, so your agent can request a review at the end of a turn.

## Trying Something Never Costs You Anything

Every one of these creates a [Self-Check](/en/latest/earnie/getting-started/first-scan#self-checks-the-dry-run-before-the-gate), not a Scan: it creates no findings and doesn't move the project's posture. It exists to tell you, or your agent, what the gate would say before anything is pushed.

## Then the Merge Gate

Merge-time checks run against the same policies your local hook already checked, [publishing a check and comment](/en/latest/earnie/using-earnie/merge-gate) on the pull request itself, so a decision made locally and one made at merge time never disagree.

## What's Next

Read the full [Earnie CLI](/en/latest/earnie/using-earnie/earnie-cli) reference, or see how a [Self-Check](/en/latest/earnie/getting-started/first-scan#self-checks-the-dry-run-before-the-gate) fits alongside a full Scan.