AI TOOLS RADAR
Todos los Skills / MARIUSFLORESCU
mariusflorescu/pstack-t3

principle-migrate-callers-then-delete-legacy-apis

Apply when introducing a new internal API while old callers still exist.

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/mariusflorescu/pstack-t3 --skill principle-migrate-callers-then-delete-legacy-apis

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.

Migrate Callers Then Delete Legacy APIs

  • Update tests to assert the new contract, and delete tests that only protect pre-refactor implementation details

When this applies:

  • No external users depend on backward compatibility
  • The project can absorb coordinated breaking changes
  • The new API is part of a simplification or refactor initiative

Relacionados por tarea

elastic
Comunidad

kibana-agent-builder

Create and manage Kibana Agent Builder agents and custom tools. Use when asked to create, update, delete, test, or inspect agents or tools in Agent Builder, or when the user wants to understand what agents or tools already exist.

Instalaciones / 1h
2
GitHub Stars
599
Actualizado
22 oct
Apache-2.03 Archivos
Ver detalles →

Motivo de la selección: Desarrollo
Palabras clave comunes: delete · exist

cursor
Comunidad

principle-redesign-from-first-principles

Apply when integrating a new requirement into an existing design.

Instalaciones / 1h
3
GitHub Stars
13,2 mil
Actualizado
20 oct
1 Archivos
Ver detalles →

Motivo de la selección: Desarrollo
Palabras clave comunes: principle · Apply

shubhamsaboo
Comunidad

commit-archaeologist

- Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite, refactor, or risky edit. Runs entirely locally.

Instalaciones / 1h
1
GitHub Stars
140,6 mil
Actualizado
30 sept
Apache-2.04 Archivos
Ver detalles →

Motivo de la selección: Desarrollo
Palabras clave comunes: introducing · exist

ryanditjia
Comunidad

principle-redesign-from-first-principles

Apply when integrating a new requirement into an existing design. Redesign as if the requirement had been a foundational assumption from day one, instead of bolting it on.

Instalaciones / 1h
1
GitHub Stars
0
Actualizado
2 oct
MIT2 Archivos
Ver detalles →

Motivo de la selección: Desarrollo
Palabras clave comunes: principle · instead · Apply

del mismo repositorio

Más Skills

Todos los Skills
mariusflorescu
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
13
Actualizado
20 oct
MIT2 Archivos
Ver detalles →
mariusflorescu
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', or reviewing a small diff you don't trust.

Instalaciones / 1h
1
GitHub Stars
13
Actualizado
20 oct
MIT2 Archivos
Ver detalles →
mariusflorescu
Comunidad

correct

Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.

Instalaciones / 1h
1
GitHub Stars
13
Actualizado
20 oct
MIT2 Archivos
Ver detalles →
mariusflorescu
Comunidad

maintain-formal-verification-skill

Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.

Instalaciones / 1h
1
GitHub Stars
13
Actualizado
20 oct
MIT2 Archivos
Ver detalles →