haystackeditor

Stop Rules — Development skill for Claude Code

Development community

Holds your coding agent to your team's written coding rules.

How to install Stop Rules

This entry records only its repository, not the path inside it, so there is no exact command to give. Open haystackeditor/stop-rules and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Stop Rules does

Holds your coding agent to your team's written coding rules. A stop hook for Claude Code, Codex, Cursor and ten more agents that asks Jev whether each changed piece breaks a rule, and hands the piece back to the agent.

Alternatives in Development

Post Everywhere — Publish one piece of content — text, image, or video — to every connected platform (or a chosen subset) in a s 212 ★
Clarity Interview — Co-write a piece with clarity, starting from an interview 189 ★
Voice Guard — Use to check ONE already-written piece of copy against a voice guide before it ships — it spawns ONE fresh sib 130 ★

README

stop-rules

`stop-rules` holds your coding agent to your team's written coding rules. When the agent finishes a turn, it cuts the code changed since the last check into pieces, one git diff hunk each, and asks [Jev](https://typesafe.ai) one yes or no question per piece and per rule, with 25 lines of the surrounding file so the question can be answered. If a rule is likely broken, it hands that piece of code back to the agent so it fixes it before you see it. Jev is the default judge; OpenAI's `gpt-6-luna` is the other one, see [Which judge](#which-judge).

![The stop-rules demo: a Claude Code window where the agent ends its turn, the Stop hook fires, and Jev and GPT-6 Luna check the same change side by side; Jev answers in 0.20 s, Luna in 2.64 s, the code goes back, the agent fixes it, and the second check is clean](examples/demo/stop-rules-demo.gif)

[examples/demo/README.md](examples/demo/README.md) explains the demo, where every number on it comes from, and the commands that reproduce the checks.

Cutting by git diff hunk is the default, and it needs nothing installed. A team that would rather have one whole function per piece switches to tree-sitter with `init --cut functions`, which is 10 languages and a few megabytes of grammar files. Both are in [docs/TUNING.md](docs/TUNING.md).

Using a coding agent? Point it at [AGENT-SETUP.md](AGENT-SETUP.md) and let it do the install.

Quick start, just you

git clone https://github.com/haystackeditor/stop-rules
node stop-rules/bin/stop-rules.mjs init --dir /path/to/your/repo

No `npm install`, no build: `bin/stop-rules.mjs` is committed and ready to run.

`init` finds which coding agents your repo already uses, copies itself into `.stop-rules/stop-rules.mjs` there, writes a starter `.stop-rules.md`, and wires the hook into each agent's own config file. That is one file of 390 KB and no grammar files at all, because cutting by git diff hunk parses nothing. It says so: