convez.ai
Skill
ripplo

claude-plugin

ripplo/claude-plugin

Ver no GitHub
InicialPluginScore · de 0 a 100

Ripplo plugin for Claude Code — e2e workflow testing skills

Instalação

$npx convez-ai ripplo/claude-plugin

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
7
Forks
0
Acompanhando
0
Saúde
42%
Último commit
há 3 dias
Versão
—
Issues abertas
0
Contribuidores
1

README

A tradução para o português deste README ainda está na fila.

Ripplo — Claude Code Plugin

Validation-loop hooks that keep your agent's tests in step with the code it ships. Part of Ripplo — typed end-to-end tests with real backend state.

Install

The plugin shells out to the ripplo CLI, so authenticate first:

npx ripplo auth login

Then in Claude Code:

/plugin marketplace add ripplo/claude-plugin
/plugin install ripplo
/ripplo:setup

/ripplo:setup runs ripplo init (scaffolds .ripplo/, writes RIPPLO_* env vars, installs @ripplo/testing), starts ripplo daemon as a background process, and mounts the engine adapter into your app server.

What the hooks do

Four hooks wire into the agent's workflow so tests are load-bearing, not advisory.

  • UserPromptSubmit nudges when user-facing code has drifted from .ripplo/tests and surfaces the flows in scope during plan mode.
  • PreToolUse / ExitPlanMode blocks plan exit if the plan touches user-facing code but no matching .ripplo/tests flow is planned.
  • PostToolUse (Edit/Write) lints the DSL on .ripplo/** edits and flags user-facing edits with no matching test.
  • Stop lints, runs scoped and changed tests, and blocks on drift — user-facing changes without a matching .ripplo/tests update.

The plugin treats src/**, app/**, apps/**, pages/**, routes/**, and components/** as user-facing, and ignores generated and vendor output.

Skills

SkillDescription
/ripplo:setupWire the engine adapter into your app server
/ripplo:exploreCrawl your codebase and generate test specs
/ripplo:createCreate a new test spec
/ripplo:scopeManage Testing Scope (visible to the user in Developer Mode)
/ripplo:runRun tests in parallel
/ripplo:debugDebug failures using DOM snapshots and network traces

Testing Scope

Scope is the agent's working memory for what user flows the current session is on the hook for. It lives in the dev-session DB (no local file) and is mutated only via npx ripplo scope add|link|remove. Agent scope items must reference an existing test (stub or implemented); free-text intents come from the user via the dashboard, and the agent's job is to stub a matching test and scope link it. The user sees live scope in Developer Mode → Testing Scope and can pause hooks entirely from there.

Lockfile

ripplo init writes the initial .ripplo/ripplo.lock. Commit it; the Ripplo server reads it on every push webhook. Keep it fresh via npx ripplo compile, or rely on the pre-commit hook /ripplo:setup installs.

Ver o original no GitHub

Bom para

Relacionados