Crickets - Primitivos de Agentes para Ciclo de Vida de Desenvolvimento
alexherrero/crickets
Ciclo dev phase-gated com kill-switches, guardrails PII e code review automatizado
Ver no GitHubAgent com plugins nativos para Claude Code e Antigravity que implementa workflows phase-gated (planejar → construir → revisar → lançar), controles de segurança production-grade, detecção de PII, revisão adversarial de PRs e reparo automático de dependências. Um framework completo de primitivos reutilizáveis que você leva para qualquer projeto, funcionando ao lado do Agent M para persistência de estado.
Instalação
npx convez-ai alexherrero/crickets1 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
Casos de uso
- Automação de ciclos de vida completos de desenvolvimento (plan → build → review → release)
- Implementação de guardrails de segurança (PII detection, kill-switches, crash recovery)
- Revisão adversarial automática de diffs e PRs para encontrar bugs
- Reparo automático de PRs do Dependabot com análise de CI e changelog
- Manutenção de documentação wiki com atualização automática e sincronização de voz
Veredito

Crickets é um framework robusto e bem-estruturado para quem precisa de automação production-grade no ciclo de desenvolvimento. A arquitetura modular com plugins gerados de uma única fonte de verdade mostra engenharia sólida, embora exija experiência avançada com agents e pipelines CI/CD para aproveitamento máximo.
README
A tradução para o português deste README ainda está na fila.
Crickets is a set of agent primitives — skills, sub-agents, hooks, commands — grouped into native plugins for Claude Code and Antigravity, generated from a single source of truth. These are the primitives you carry into any project: the phase-gated dev loop, safety controls, code review, docs upkeep.
It pairs with Agent M, the memory — auto-recall and on-disk state that follow you across every project.
What's new lives in the CHANGELOG.
What's inside
Six plugins, generated from one source. Together they cover the working day with an agent:
- Run a phase-gated dev process — plan → work → review → release, working the plan autonomously with a per-task safety check.
- Stay in control of a running agent — an emergency stop, mid-run redirection, and crash recovery that never touches your branch.
- Review any diff or PR adversarially — a reviewer primed to find bugs, not to agree.
- Fix Dependabot PRs automatically — reads the failing CI and the changelog, patches, never merges.
- Keep personal information out of public commits — scan and redact before anything ships.
- Keep a wiki current, in your voice — authoring, repair, and a watcher that opens doc PRs.
Each capability is its own plugin; install only what you want. What each one ships, and how they compose, is in the plugin pages (the Plugins component under Architecture in the wiki sidebar).
How it works
flowchart LR
S[src/<group>/<br/>one source of truth<br/>kind · supported_hosts · requires]
G[scripts/generate.py<br/>deterministic emit]
CC[dist/claude-code/plugins/<group>]
AG[dist/antigravity/plugins/<group>]
S --> G
G --> CC
G --> AG
Author a primitive once under its group. The generator emits a native Claude Code plugin and a native Antigravity plugin per group, plus each host's marketplace manifest. The committed dist/ is what ships, and a CI gate (generate.py check) fails the build if dist/ drifts from src/. Where the two hosts diverge — hook events, dependency handling, the snippet→rules/ gap — is spelled out in Per-Host-Paths and Compatibility.
Get started
Install the recommended set on whichever host(s) you have:
curl -fsSL https://raw.githubusercontent.com/alexherrero/crickets/main/bootstrap.sh | bash
Prefer the marketplace? One word from GitHub on Claude Code:
claude plugin marketplace add alexherrero/crickets
claude plugin install developer-workflows@crickets # + developer-safety, code-review, github-ci, pii, wiki-maintenance
All three install modes (one-liner / marketplace / manual --plugin-dir) per host: Install crickets plugins. Hacking on a plugin? Modify a crickets plugin.
Adding + developing customizations
- Tutorial 1 — Your first code review — use a plugin end-to-end.
- Plugin anatomy — what a crickets plugin is, before you change one.
- Repo layout — what lives where.
- Modify a crickets plugin — the
src/→ generate → dogfood loop. - Add a skill · Add a plugin
- Manifest Schema — primitive frontmatter +
group.yaml. - Troubleshooting — symptom-first lookup when something stops working.
License
MIT — LICENSE.