Noomoo — Git skill for Claude Code
noomoo Claude Code plugin: deterministic checks and lifecycle gates from specification to a verified pull request.
How to install Noomoo
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open TaskForceNow/noomoo and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Noomoo does
noomoo Claude Code plugin: deterministic checks and lifecycle gates from specification to a verified pull request.
Alternatives in Git
- Worktree Deliver — Commit all work, push, and create a pull request from the current worktree 23.4k ★
- Yeet — Stage, commit, push code, and open a GitHub pull request via CLI 14.6k ★
- Generate PR Description — You are tasked with generating a comprehensive pull request description following the repository's standard te 10k ★
README
noomoo
[](LICENSE)   
**English** · [Русский](README.ru.md) · [Deutsch](README.de.md) · [Español](README.es.md) · [Français](README.fr.md) · [Português](README.pt-BR.md) · [中文](README.zh-CN.md) · [日本語](README.ja.md)
Don't trust the agent. Trust the system.
**noomoo is an engineering harness for agentic software development.**
Let coding agents plan, build, test, review, and ship software inside rules your team can actually enforce.
Instead of trusting what an agent says it did, noomoo checks what happened in the repository.
Built for teams moving from AI-assisted coding to autonomous software delivery.
AI made coding cheap. Verification is the new bottleneck.
Coding agents can already implement features, fix bugs, run tests, open pull requests, and respond to review. The question is no longer: **Can the agent write the code?** The real questions are:
- Did it understand the requirement?
- Did it stay inside the task?
- Did it follow the architecture?
- Did it actually add the tests?
- Did those tests really run?
- Is the review still valid after the latest change?
- Is “done” a fact — or just something the agent said?
The agent cannot talk its way around the gate.
| Agent | noomoo |
|---|---|
| “All tests pass.” | Show the test result for this exact revision. |
| “I reviewed the change.” | Show a fresh review artifact for the current code. |
| “I only changed what the task required.” | Show the diff and prove the scope. |
| “The task is done.” | Prove it. |
Natural-language status is not proof. **Repository state is proof.**
Humans steer. Agents execute. noomoo verifies.
- **Define t
Related Skills
Dbdocs PR
Open a GitHub PR for the current branch with a body that follows .github/PULL_REQUEST_TEMPLATE.md, filled from
Claude Tmux
by Niels Groeneveld - Manage Claude Code within tmux. A tmux popup of all your Claude Code instances, enabling
PR Autopilot
Claude Code skill that orchestrates the full Pull Request lifecycle — creation, multi-agent review, automated
Whiletrue
Local Python orchestrator that runs pipelines of agent and deterministic steps around Claude Code, opencode an
Commit And PR
Let's commit the changes. Run tests, typechecks, and format checks. Then commit, push, and create a pull reque
PR Checks
Show current PR's check status; pull failure logs if any are red
Related Agents
Fleet Review
Review changes for defects: a diff, branch, pull request, plan, or specification. Runs on opus.
PR Manager Agent
Pull request workflow specialist for PR creation and lifecycle via the Agent tool.
PR Fixer
Use to resolve findings on an existing pull request - review comments, CI failures, and self-review findings -