# Verify Work Skill (The Gatekeeper)

A skill that enforces "The Iron Law": **No completion claims without fresh verification evidence.**

It prevents the "Hallucinated Success" problem where an AI agent claims "I fixed it" because the code *looks* right, even though it fails to compile or pass tests.

## Features

*   **Universal Verification:** Automatically detects project type (Nix, Node, Rust, Python, Go, Make) and runs the appropriate checks.
*   **Zero-Config:** Works out of the box for standard project structures.
*   **Strict Gate:** Instructs the agent that it is *forbidden* from claiming success if verification fails.

## Usage

### For Agents
The agent invokes this skill whenever it believes a task is done.

```bash
# Agent runs this
./skills/verify-work/scripts/verify.sh
```

### For Humans
You can run the script manually to verify the current directory:

```bash
# Verify the current project
~/.claude/skills/verify-work/scripts/verify.sh
```

## Supported Project Types

1.  **Nix:** `flake.nix` -> `nix flake check`
2.  **Rust:** `Cargo.toml` -> `cargo test && cargo build`
3.  **Node/TS:** `package.json` -> `npm test`, `npm run build`
4.  **Python:** `pyproject.toml`/`requirements.txt` -> `pytest` or `unittest`
5.  **Go:** `go.mod` -> `go test ./...`
6.  **Makefile:** Target `test`, `build`, or `all`

## Philosophy

This skill is the "Gatekeeper". Ideally, it runs *after* code changes but *before* `code-review` or `test-review`.

1.  **Verify-Work:** Does it compile/pass? (If No -> STOP).
2.  **Test-Review:** Are the tests meaningful?
3.  **Code-Review:** Is the code maintainable?
