convez.ai
SkillDevOps & InfraestruturaIntermediário
Groupe-Agel

Clever Cloud Assistant

Groupe-Agel/clever-cloud-assistant

Skills e agents para Clever Cloud: deploys seguros, migrações e CI/CD sem surpresas

Ver no GitHub
InicialPluginScore · de 0 a 100

Extension pack para Claude Code que codifica as práticas certas para desenvolver em Clever Cloud. Inclui skills, agents e commands para deploys, migrações de banco de dados, health checks e pipelines de CI/CD, evitando os problemas conhecidos da plataforma.

Instalação

$npx convez-ai Groupe-Agel/clever-cloud-assistant

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
50%
Último commit
há 4 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Automatizar deploys em Clever Cloud com validação pré-voo e verificação de saúde
  • Executar migrações de banco de dados no hook correto sem race conditions
  • Configurar pipelines GitHub Actions para CI/CD em Clever Cloud
  • Streamar logs filtrados e monitorar status de aplicações

Veredito

Ferramenta especializada que resolve problemas reais e repetitivos em Clever Cloud (hooks na ordem errada, migrações com race condition, logs que não fecham). Ideal para quem já usa Clever Cloud e quer economizar horas em troubleshooting de infraestrutura.

README

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

clever-cloud-assistant

A Claude Code extension pack that knows Clever Cloud cold.

What it solves

Building on Clever Cloud means re-learning the same sharp edges again and again: hooks that fire in the wrong order, migrations that race the app start, SSH deploys that silently diverge from CLI deploys, log commands that dump noise instead of signal. This pack codifies the fixes so you stop losing hours to infrastructure friction.

Pain points covered (see docs/known-gotchas.md for the full list):

  • Migrations placed in CC_PRE_BUILD_HOOK fail with "Cannot find module" — it fires before npm install; the correct hook is CC_PRE_RUN_HOOK
  • Drizzle journal regressions: edited "when" timestamps make migrations silently skip, leaving prod code expecting columns the DB doesn't have
  • CC_PRE_RUN_HOOK runs on every instance on horizontal scale — non-idempotent migrations race each other
  • clever logs | tail hangs forever — the stream never closes; you need --until to get a snapshot
  • "Deploy succeeded" ≠ "app healthy" — clever deploy exits at deploy-end; without CC_HEALTH_CHECK_PATH a crashed app goes unnoticed
  • Two confusable SSH hosts (git push vs instance gateway) and zone names that aren't the marketing region names
  • Force-push panic: CC rewrites its remote history by design, so non-fast-forward is expected
  • clever env import silently deletes all existing variables
  • Build-affecting env vars need a full redeploy, not a restart — and .git is deleted during build (CC_COMMIT_ID instead of git rev-parse)
  • No project CLAUDE.md for CC apps, so Claude has no app IDs, zone, or deploy method in scope

What's included

ComponentNameWhat it does
Skillcc-deployDeploy via CLI or SSH with pre-flight validation
Skillcc-migrationsRun migrations safely with correct hook placement
Skillcc-healthcheckVerify app health after deploy
Skillcc-cicdSet up GitHub Actions → CC CI/CD pipeline
Agentcc-opsHaiku agent for all CC CLI operations
Command/cc-deployOne-command deploy with health check
Command/cc-logsFiltered log streaming
Command/cc-statusApp status matrix
Hookcc-pre-deploy-validateAdvisory pre-deploy checks
TemplateCLAUDE.md.templateDrop-in CLAUDE.md for any CC project
Templatesdeploy-test.yml, migrations-check.ymlReady-to-use GitHub Actions workflows
Docsknown-gotchas.md17 production-incident-sourced CC pain points and fixes

Quick install

Windows (PowerShell):

.\install.ps1 -RegisterHook

macOS / Linux / Git Bash:

./install.sh --register-hook

This copies skills, agent, commands, and the hook into ~/.claude/, and (with the flag) registers the pre-deploy hook in ~/.claude/settings.json (backup taken first). Restart your Claude Code session afterwards.

Copying the hook file alone does nothing — PreToolUse hooks must be registered in settings.json. The installer handles it; doing it manually, add under hooks.PreToolUse (matcher "Bash"): { "type": "command", "command": "bash ~/.claude/hooks/cc-pre-deploy-validate.sh" }

Usage

# Deploy to staging with pre-flight checks and health verification
/cc-deploy --app test

# Deploy to production
/cc-deploy --app prod

# Stream filtered logs from the last 30 minutes
/cc-logs --since 30m --filter error

# Show status matrix across all configured apps
/cc-status

Project CLAUDE.md

Copy templates/CLAUDE.md.template to your project root and fill in your app IDs, zone, and migration config. This gives Claude the context it needs to run CC operations without asking.

cp templates/CLAUDE.md.template ./CLAUDE.md
# Fill in the {{...}} placeholders: {{APP_TEST_ID}}, {{APP_PROD_ID}}, {{ZONE}},
# {{MIGRATE_COMMAND}}, {{HEALTH_ENDPOINT}}, ...

For CI/CD, copy the GitHub Actions templates too:

cp templates/.github/workflows/deploy-test.yml      .github/workflows/
cp templates/.github/workflows/migrations-check.yml .github/workflows/
# deploy-test.yml: set your test app ID + push host; add CLEVER_SSH_KEY secret
# migrations-check.yml: set JOURNAL_DIR to your migrations path

Requirements

  • Claude Code CLI
  • Clever Cloud CLI (clever) — required for Method A deploys
  • SSH deploy key configured on your CC app — required for Method B deploys
  • jq — optional; the hook uses it when present and falls back to shell parsing without it (CI workflows do require it, but it's preinstalled on ubuntu-latest)

License

MIT — AGEL GROUP

Ver o original no GitHub

Bom para

Relacionados