# Xray Hermes Plugin Installed

**Restart your Hermes session** for the plugin to take effect.

## What's Installed

| Component | Description |
|-----------|-------------|
| `xray_validate` | Pre-commit validation with quality gates |
| `xray_codex_check` | Code review against 60 Codex error-prevention rules |
| `xray_health` | Framework health check |
| `xray_hooks` | Git hooks management (install, uninstall, list, status) |
| `pre_tool_call` hook | Quality gates + nudges before every tool call |
| `post_tool_call` hook | Post-processors after every tool call |

## Git Hooks

The plugin can install git hooks for automated validation:

| Hook | Type | Description |
|------|------|-------------|
| `pre-commit` | Blocking | TypeScript check + Codex validation before commit |
| `post-commit` | Non-blocking | Log archival + cleanup after commit |
| `pre-push` | Blocking | Full validation suite before push |
| `post-push` | Non-blocking | Comprehensive monitoring after push |

### Install Hooks

```
/xray hooks install
```

Or use the tool directly:
```
xray_hooks(action="install")
```

### Check Hook Status

```
/xray hooks status
```

### Uninstall Hooks

```
/xray hooks uninstall
```

## Quick Test

After restarting Hermes, try:

```
/xray status
/xray stats
```

Or use the tools directly — `xray_health` will confirm the bridge is connected.

## MCP Servers

The plugin works alongside Xray's MCP servers (if configured in your
Hermes config). The plugin's native tools provide offline/offline-first
validation, while MCP servers offer deeper framework integration.

## Files

The plugin lives at `~/.hermes/plugins/xray-hermes/`. It is auto-updated
when you run `npm install` or `npm update` in a project with `0xray`
as a dependency.