michael-denyer/pstack-claude

bro

Restate the last message in plain human language, with no jargon.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/michael-denyer/pstack-claude --skill bro

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Restate your last message. Stop using jargon and speak coherently. State it more simply and concisely, like one human talking to another.

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
michael-denyer
Comunidad

architect

Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.

Instalaciones / 1h
1
GitHub Stars
4 mil
Actualizado
4 nov
michael-denyer
Comunidad

babysit

Watch an open PR — fix failing CI, handle the straightforward review comments, and drive it to a mergeable state. Claude Code analog of Cursor's built-in /babysit. Use after opening a PR when the user wants the agent to shepherd it without re-prompting.

Instalaciones / 1h
1
GitHub Stars
4 mil
Actualizado
4 nov
michael-denyer
Comunidad

benchmark-checklist

Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.

Instalaciones / 1h
1
GitHub Stars
4 mil
Actualizado
4 nov
michael-denyer
Comunidad

blast-radius

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.

Instalaciones / 1h
1
GitHub Stars
4 mil
Actualizado
4 nov