convez.ai
SkillAutomaçãoAvançado
surahli123

Coding Agent Setup

surahli123/coding-agent-setup

Workflows determinísticos e config modular para agentes de código Claude

Ver no GitHub
InicialPluginScore · de 0 a 100

Configuração reutilizável para agentes de código Claude com workflows determinísticos, skills, hooks e gestão de privacidade. Inclui padrões de orquestração multi-agente (swarms de revisão adversarial, pesquisa paralela) e config templada para roteamento de sub-agentes.

Instalação

$npx convez-ai surahli123/coding-agent-setup

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
0
Forks
0
Acompanhando
0
Saúde
28%
Último commit
há 4 meses
Versão
—
Issues abertas
1
Contribuidores
1

Casos de uso

  • Orquestração multi-agente paralela com gates de qualidade
  • Workflows de revisão adversarial automática (correctness, contract, security)
  • Pesquisa e síntese paralela com otimização de custo (Sonnet + Opus)

Veredito

Setup técnico bem documentado para quem precisa orquestrar agentes Claude em workflows complexos. O padrão de swarm adversarial e pesquisa paralela são úteis, mas requer domínio de Claude Code e hooks para aproveitar plenamente.

README

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

coding-agent-setup

My coding-agent setup — reusable workflows plus privacy-sanitized Claude Code/OMC config, skills, hooks, and settings.

Contents

  • workflows/ — Claude Code dynamic workflow scripts (deterministic multi-agent orchestration)
    • review-swarm.js — adversarial review gate: deterministic test/lint gate → 3 parallel adversarial Sonnet reviewers (correctness / contract / security) → barrier-merged verdict; the human is the Referee.
    • x-research.js — X/Twitter deep research: 4 parallel Sonnet agents (4 lenses) → 1 Opus synthesis. Cost-disciplined (mechanical → Sonnet, synthesis → Opus).
  • docs/ — how this setup is built
    • building-workflows.md — design decisions + the debugging lessons behind the workflows.
  • config/ — my privacy-sanitized coding-agent config (templated where personal)
    • CLAUDE.md + dot-claude/CLAUDE.md — global instructions & subagent routing (identity/domain are _Personalize_ placeholders).
    • dot-claude/settings.json + dot-claude/hooks/ — permissions, hook wiring, and the hook scripts (ledger, gates, budgets).
    • dot-claude/refs/ — lazy-loaded playbooks (circuit-breaker, evidence-first, karpathy, …) + rule rationale.

Install the workflows

cp workflows/*.js ~/.claude/workflows/

Then invoke from Claude Code — e.g. Workflow({ name: "review-swarm", args: "/abs/path/to/repo" }). Each script's header documents its usage.

Heads-up: x-research depends on a local twitter CLI at ~/.local/bin/twitter — swap the TW block in the script for your own X-search tool if yours differs.

Status

🚧 Work in progress, but functional. Workflows are tested end-to-end. config/ is a privacy-sanitized mirror of my ~/.claude — username / absolute paths / secrets removed, personal identity & domain replaced with _Personalize_ placeholders so it works as a reusable scaffold.

Why this exists

Notes-to-self, made reproducible: the orchestration patterns plus the gotchas that cost real debugging time — so the setup can be rebuilt, and so future-me doesn't relearn them.

Ver o original no GitHub

Bom para

Relacionados