/ Directorio / Playground / Code Review Skill (awesome-skills)
← Todos los servidores ↗ GitHub
● Comunidad awesome-skills ⚡ Instantáneo

Code Review Skill (awesome-skills)

por awesome-skills · awesome-skills/code-review-skill

Comprehensive Claude Code code-review skill covering React 19, Vue 3, Rust, TypeScript, TanStack Query v5, and more frameworks.

Code Review Skill (awesome-skills) is a Claude skill maintained by awesome-skills. Comprehensive Claude Code code-review skill covering React 19, Vue 3, Rust, TypeScript, TanStack Query v5, and more frameworks. See README for installation and configuration: https://github.com/awesome-skills/code-review-skill

▶ Ver demo 📦 Instalar 💡 Casos de uso

Por qué usarlo

Características clave

Demo en vivo

Cómo se ve en la práctica

awesome-skills-code-review.replay ▶ listo
0/0

Instalación

Repositorio del autor · Documentación oficial de Skills de Claude

Casos de uso

Usos del mundo real: Code Review Skill (awesome-skills)

Use Code Review Skill (awesome-skills) for its primary workflow

👤 Claude Code users ⏱ ~20 min intermediate

Cuándo usarlo: See repo README for canonical use cases.

Requisitos previos
  • Repo cloned or installed — See https://github.com/awesome-skills/code-review-skill
Flujo
  1. Install
    Install Code Review Skill (awesome-skills) per README.✓ Copiado
    → Tool registered with client
  2. Configure
    Provide credentials/config as instructed.✓ Copiado
    → Successful auth/init
  3. Use
    Run a sample task with Code Review Skill (awesome-skills).✓ Copiado
    → Expected output

Resultado: You can drive the documented workflow end-to-end.

Errores comunes
  • Skipping README — Read the repo README and CHANGELOG before shipping to prod.

Herramientas

Lo que expone este MCP

HerramientaEntradasCuándo llamarCoste
primary see README Primary action free

Coste y límites

Lo que cuesta ejecutarlo

Cuota de API
None of its own; bounded by upstream provider quotas if any
Tokens por llamada
Depends on usage
Monetario
Open source — check repo LICENSE
Consejo
Review upstream API costs (if any) before automating.

Seguridad

Permisos, secretos, alcance

Ámbitos mínimos: Whatever the upstream provider requires
Almacenamiento de credenciales: Env vars or local config — never commit secrets
Salida de datos: Forwards data per its README
No conceder nunca: Full admin to untrusted prompts

Resolución de problemas

Errores comunes y soluciones

Auth fails

Verify credentials and required scopes match README.

Verificar: Re-read repo README auth section.
Tool not found by client

Ensure MCP client config points to correct command/path.

Verificar: Restart the client after editing config.

Más

Recursos

📖 Lee el README oficial en GitHub

🐙 Ver issues abiertas

🔍 Ver todos los 400+ servidores MCP y Skills