menhera-loop
New"Done" means nothing — a menhera-style completion gate for Claude Code that blocks empty completion claims until tests actually ran green and no TODOs are left behind.
Summary
The menhera-loop skill enforces a strict completion gate for Claude Code, ensuring that no task is marked 'done' until all tests pass and no TODOs remain.
- It prevents premature claims of completion, helping developers maintain quality and avoid overlooked issues in their workflow.
Install & Usage
mkdir -p .claude/skillsAdd the configuration to .claude/skills/menhera-loop.md
/menhera-loopUse Cases
Usage Examples
/menhera-loop run tests and check for TODOs before marking this task complete
Run the test suite and list any remaining TODOs in the codebase
Verify that all tests pass and no TODO comments exist, then confirm completion
Security Audits
Frequently Asked Questions
What is menhera-loop?
The menhera-loop skill enforces a strict completion gate for Claude Code, ensuring that no task is marked 'done' until all tests pass and no TODOs remain. It prevents premature claims of completion, helping developers maintain quality and avoid overlooked issues in their workflow.
How to install menhera-loop?
To install menhera-loop: create the skills directory (mkdir -p .claude/skills), then add the config to .claude/skills/menhera-loop.md. Finally, /menhera-loop in Claude Code.
What is menhera-loop best for?
menhera-loop is a other categorized under General. It is designed for: testing. Created by Borelchu.
What can I use menhera-loop for?
menhera-loop is useful for: Block a pull request from being marked complete until all unit tests pass and no TODOs are present.; Enforce a quality gate before merging a feature branch, requiring test success and TODO resolution.; Automatically verify that code changes don't introduce new TODOs or break existing tests before allowing a commit.; Integrate into a CI pipeline to prevent deployment if tests fail or TODOs are left unresolved.; Ensure that a refactoring task is truly finished by checking for test failures and leftover TODO comments.; Use as a personal discipline tool to avoid claiming work done without verifying test results and TODO cleanup..