MarioCwejman

Quality Loop — Development skill for Claude Code

Development community

A verification-first working layer for Claude Code: hooks that gate edits on real syntax checks, reviewer agents that judge the rendered result, and skills for onboarding a repo and capturing what you.

How to install Quality Loop

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

What Quality Loop does

Alternatives in Development

Discipline — Toggle discipline mode — auto-invoke verification, brainstorming-before-coding, and review checks 2.8k ★
05 Public Permalink — Give every published post a public read-only permalink at /p/:slug — a standalone server-rendered 143 ★
Bm Doctor — Diagnose and recover basemind when it isn't working (MCP tools missing/erroring, "no index", dead server) — ru 94 ★

README

quality-loop

A verification-first working layer for Claude Code.

The premise is that output quality is set by constraints and feedback loops rather than by model choice. So this adds three things: hooks that refuse to let an edit pass unchecked, reviewer agents that judge the rendered result instead of the intent, and skills that put knowledge where it survives past the session.

The thing it is actually built to stop: Claude ending a turn saying something works when nothing has been run.

**[Read the manual](https://MarioCwejman.github.io/quality-loop/guide.html)** — or the [overview](https://MarioCwejman.github.io/quality-loop/). Source in [`docs/`](docs/).

Install

Requires [Node.js](https://nodejs.org) on your `PATH` for the hooks. Language checkers are optional — each is skipped when the tool is absent rather than failing.

git clone https://github.com/MarioCwejman/quality-loop.git
cd quality-loop
claude plugin marketplace add ./dist
claude plugin install quality-loop@mario-cwejman

Then start a new session — skills, agents and hooks are read when a session opens.

Check what landed:

claude plugin details quality-loop@mario-cwejman

Four skills, three agents and three hook events.

Also copy the global layer

A plugin can carry skills, agents, commands, hooks and MCP servers. There is **no `rules` component**, and no way to ship a global `CLAUDE.md`. Those parts live in [`global-layer/`](global-layer/) and are copied by hand:

cp -r global-layer/rules ~/.claude/rules
cp global-layer/CLAUDE.md ~/.claude/CLAUDE.md

Edit the "Where things live" section of `CLAUDE.md` afterwards — it is the only machine-specific part, and it is there so Claude stops guessing where your projects and toolchain are.