Claude Checkup
buvis/claude-checkup
Audita config, filesystem, skills, contexto, MCP servers e sessões do Claude Code
Ver no GitHubSuite de auditorias e health-checks para Claude Code que detecta problemas de segurança, configuração, cache, conflitos de skills e anomalias de sessão. Combina scripts determinísticos com análise do modelo para gerar relatórios priorizados e planos de remediação.
Instalação
npx convez-ai buvis/claude-checkup1 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
- Validar permissões e detectar secrets hardcoded em configurações
- Limpar caches órfãos e memórias stale no filesystem
- Encontrar conflitos, redundâncias e skills duplicados
- Rastrear saúde de servidores MCP conectados
- Analisar padrões e anomalias em transcripts de sessão
- Gerar relatório priorizado de vulnerabilidades e remediações
Veredito

Ferramenta essencial para manutenção e higiene de ambientes Claude Code em produção. Combina checagem automatizada com julgamento do modelo, cobrindo segurança, performance e consistência — recomendado para quem gerencia múltiplas skills ou MCP servers.
README
A tradução para o português deste README ainda está na fila.
Claude Checkup
A health-check toolkit for Claude Code. Six focused audit skills plus a single orchestrator that runs them all, prints a dashboard, and produces a prioritized remediation plan. Deterministic work runs in helper scripts (so audits are reproducible); judgment calls stay with the model.
What it audits
| Skill | Catches |
|---|---|
audit-config | Loose permissions, hardcoded secrets, hook health/injection, risky MCP servers, cross-level settings conflicts |
audit-filesystem | Stale/orphaned plugin caches, orphaned and dormant project configs, memory index drift and stale memories |
audit-authoring | Skill structure/frontmatter, duplicate or confusable skills, rule conflicts/redundancy/shadowing/staleness |
audit-context | Per-component token overhead, classified as always-loaded / hidden tax / on-demand |
audit-mcp-health | Configured MCP servers vs live tools, disconnected servers, last-used tracking |
audit-sessions | Patterns, anomalies, and unused skills across past session transcripts |
audit-claude-config | Orchestrator — runs them all, prints a dashboard, builds a remediation plan |
Install
Two commands inside Claude Code:
/plugin marketplace add buvis/claude-plugins
/plugin install claude-checkup@buvis-plugins
Restart Claude Code, then run /audit-claude-config to get a full health report.
Update
/plugin update claude-checkup@buvis-plugins
Alternative: install directly from this repo
/plugin marketplace add buvis/claude-checkup
/plugin install claude-checkup@claude-checkup
Usage
audit my claude config # run everything, build remediation plan
audit my claude config fast # skip the slow session-transcript audit
Or invoke any individual audit by name, e.g. audit security, audit hooks,
audit memory, audit plugins — those phrases still route (to audit-config,
audit-config, audit-filesystem, audit-filesystem respectively).
The orchestrator saves a dated report to dev/local/audit-results/{YYYY-MM-DD}.md.
Severity grading
Each finding gets a severity, prioritized in the remediation plan:
- CRITICAL — fix now (data loss, secret exposure, broken hooks)
- HIGH — fix this week (permission escalations, conflicting rules)
- MEDIUM — fix when convenient (cleanup opportunities)
- LOW — backlog (style, minor consistency, reclaimable disk)
- INFO — context only; never implies a deletion (e.g. "usage could not be determined")
Requirements
- Claude Code with plugin support
python3on PATH (helper scripts foraudit-config,audit-filesystem,audit-context,audit-sessions)PyYAMLfor the skill validator used byaudit-authoring- Optional: warden — if installed, the
orchestrator also runs
/warden:review-decisions
License
MIT