cavaleiro-ai

Gmickel Claude Marketplace — Testing skill for Claude Code

Testing community

Faster than your agent alone.

How to install Gmickel Claude Marketplace

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

What Gmickel Claude Marketplace does

Faster than your agent alone. And better. A workflow plugin that takes a bug, idea or ticket to a verified pull request: specs, cross-model review by risk, live QA, receipts in your repo. Claude Code · Codex · Cursor · Droid · Grok Build · OpenCode · Muse Code.

Alternatives in Testing

  • Agent Skills Spec — A skill is a folder of instructions, scripts, and resources that agents can discover and load dynamically to p 1.9k ★
  • Grilling.V1 — Interview the user to clarify or stress-test the request before acting 272 ★
  • Check Invariants — Runs only the tree CRDT invariant test battery in outl-core 201 ★

README

Flow-Next

[![GitHub stars](https://img.shields.io/github/stars/gmickel/flow-next?style=flat&logo=github&label=Stars&color=2f6f5f)](https://github.com/gmickel/flow-next/stargazers) [![CI](https://img.shields.io/github/actions/workflow/status/gmickel/flow-next/test-flow-next.yml?branch=main&label=CI%20%C2%B7%203%20OS)](https://github.com/gmickel/flow-next/actions/workflows/test-flow-next.yml) [![Latest release](https://img.shields.io/github/v/release/gmickel/flow-next?label=Release&color=green)](https://github.com/gmickel/flow-next/releases/latest) [![Mentioned in Awesome](https://awesome.re/mentioned-badge.svg)](https://github.com/ithiria894/awesome-claude-code-workflows) [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)

Faster than your agent alone. And better.

**Agents generate. Flow-Next proves.**

Flow-Next is a workflow plugin for your coding agent. Hand it a bug, an idea, a ticket or a slow page, and it takes the work all the way to a pull request. It picks the route that kind of work needs, builds the change, gets it reviewed by another model family when the risk calls for it, and hands you something you can check instead of something you have to trust.

It's also fast now. On the same model, the working change comes back in about the time your agent takes on its own, often less, and a large feature in about half the time. The result is better than the plain agent's before any review runs, and review and live QA widen that gap.

You say What Flow-Next does
"This fails: " Turns the failure into a failing test, fixes the cause, and shows you the test going from red to green.
"Add passwordless login" (or the conversation you just had about it) Writes a spec with numbered acceptance criteria, builds it, has it reviewed, and opens a PR that maps every change to a criterion when you ask for one.
"The /reports page takes four seconds, it should take