brownjuly2003-code

Myflow Controller — Testing skill for Claude Code

Testing community

A controller for AI coding agents that takes 'done' away from the model: a Claude Code skill plus a stdlib-only Python controller (test gate, scope by delta, tracked review findings, budgets, observab.

How to install Myflow Controller

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

What Myflow Controller does

Alternatives in Testing

Test Runner — Run Python tests with pytest, unittest, or other testing frameworks 23.4k ★
Pua — Use when the user invokes /pua or asks for PUA mode, try-harder/retry help, change-approach coaching, completi 19.5k ★
OpenAgentsControl — AI agent framework for plan-first development workflows with approval-based execution 4.8k ★

README

MyFlow

**A controller for AI coding agents that takes the word "done" away from the model.**

MyFlow is a [Claude Code](https://claude.com/claude-code) skill (`/myflow_new`) plus a controller written in plain Python (standard library only). Claude Code is the orchestrator: it turns a goal into tasks and drives the controller's commands. Separate model processes write the code and review it. The controller owns everything that must not depend on a model's opinion: the order of the steps, the test gate, what a change is allowed to touch, every review finding and what happened to it, the budget, and the proof that the commit is exactly the tree that passed the gate.

**Status.** A personal tool, used every day on the author's own projects since late August 2026 and published as it is. Windows-first. The skill prompt (`SKILL.md`) and the full reference (`docs/help.ru.md`) are in Russian; the controller, its output and the documents linked below are in English. The default model chains name the CLIs and subscriptions the author has, so expect to change them (see [Choosing models](#choosing-models)).

Why

A coding agent writes the code and then decides that the code is finished: it wrote it, it looked at it, it says "done". The checker and the checked are the same party, and on long runs that fails in predictable ways: tests that never ran reported as green, edits made after the review slipping into the commit, review comments going round in circles, a second pass quietly undoing the first, a compacted context that forgot what was decided.

MyFlow separates the two. Between "the model wrote it" and "the work is accepted" there is a program that understands nothing about the intent and does one thing: it runs the checks and counts the result. It does not believe text from a model; it looks at files, command output, exit codes and the hash of the working tree. A model may say "all tests pass" as often as it likes: if no test ran, the controller does not print