AI TOOLS RADAR
Tutti gli Skills / MARIUSFLORESCU
mariusflorescu/pstack-t3

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

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

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/mariusflorescu/pstack-t3 --skill principle-migrate-callers-then-delete-legacy-apis

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

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

Correlati per attività

elastic
Community

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.

Installazioni / 1h
2
GitHub Stars
599
Aggiornato
22 ott
Apache-2.03 File
Vedi dettagli →

Motivo della selezione: Sviluppo
Parole chiave comuni: delete · exist

cursor
Community

principle-redesign-from-first-principles

Apply when integrating a new requirement into an existing design.

Installazioni / 1h
3
GitHub Stars
13,2K
Aggiornato
20 ott
1 File
Vedi dettagli →

Motivo della selezione: Sviluppo
Parole chiave comuni: principle · Apply

shubhamsaboo
Community

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.

Installazioni / 1h
1
GitHub Stars
140,6K
Aggiornato
30 set
Apache-2.04 File
Vedi dettagli →

Motivo della selezione: Sviluppo
Parole chiave comuni: introducing · exist

ryanditjia
Community

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.

Installazioni / 1h
1
GitHub Stars
0
Aggiornato
2 ott
MIT2 File
Vedi dettagli →

Motivo della selezione: Sviluppo
Parole chiave comuni: principle · instead · Apply

dallo stesso repository

Altri Skills

Tutti gli Skills
mariusflorescu
Community

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.

Installazioni / 1h
1
GitHub Stars
13
Aggiornato
20 ott
MIT2 File
Vedi dettagli →
mariusflorescu
Community

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.

Installazioni / 1h
1
GitHub Stars
13
Aggiornato
20 ott
MIT2 File
Vedi dettagli →
mariusflorescu
Community

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.

Installazioni / 1h
1
GitHub Stars
13
Aggiornato
20 ott
MIT2 File
Vedi dettagli →
mariusflorescu
Community

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.

Installazioni / 1h
1
GitHub Stars
13
Aggiornato
20 ott
MIT2 File
Vedi dettagli →