Explorar comunidad

Una implementación de servidor Model Context Protocol (MCP) que proporciona interacción entre Elasticsearch y OpenSearch. — Autor: cr7258 — Estrellas: 295

El servidor MCP ayuda a los modelos a comprender mejor su aplicación Vite/Nuxt. — Autor: antfu — Estrellas: 910

Observa los sitios web de tus competidores y te dice qué cambió. Cada semana rastrea sus precios, productos y mensajes. — Autor: Competitor Tracker & Co.

Servidor MCP para Floors.live: diseñe planos de planta para eventos, administre listas de invitados y ejecute asignaciones de asientos inteligentes. — Autor: Hakolsound

Plataforma de negociación de CFD Integración MCP — Autor: capital-com-sv — Estrellas: 4

Run automated accessibility checks on changed routes, fix violations, and repeat until the audit is clean.

When a check fails twice the same way, append a guardrail sign to .ralph/guardrails.md so the next iteration avoids repeating it.

After code changes, find affected docs and update README, API references, and inline comments to match.

Fix high/critical npm audit findings one at a time with test verification — not a blind npm audit fix --force.

Run the formatter, fix any remaining style issues, and loop until the codebase formats cleanly with no diffs.

After shipping a feature, loop until CHANGELOG.md has a user-facing entry and conventional commits are reflected.

Implement from a written spec.md checklist — each iteration completes one unchecked requirement with verification.

Run failing tests repeatedly, classify each failure as flaky or real, and fix only confirmed regressions.

When implementation claims done, a separate verifier pass runs build, lint, and tests with no access to the implementer's rationale.

Run the production build, fix compile and bundling errors, and loop until the build succeeds.

On an interval, hit health and smoke endpoints after a deploy until all checks return healthy responses.

Run end-to-end tests, fix UI and integration failures, and loop until the E2E suite passes.

Run Playwright or Percy visual snapshots on UI changes; fix unintended diffs until baselines match intentionally.

Add focused tests until coverage meets your threshold (e.g. 80%), without changing production behavior unnecessarily.

Upgrade a single outdated package per iteration, fix breakages, and commit — safer than bulk npm update.

Every 15 minutes, inspect open PRs with a watch label: nudge reviewers, fix CI, rebase if behind main.

Test-first loop: write a failing test, implement the minimum code to pass, refactor, and repeat.

Run lint and typecheck, fix reported issues, and loop until the codebase is clean.

Run your test suite, fix the smallest root cause on failure, and repeat until every test passes.