AI TOOLS RADAR
All skills / MARIUSFLORESCU
mariusflorescu/pstack-t3

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

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

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/mariusflorescu/pstack-t3 --skill principle-migrate-callers-then-delete-legacy-apis

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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

Related by task

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.

1h installs
2
GitHub stars
599
Updated
Oct 22
Apache-2.03 Files
View skill details →

Why explore this: Development
Shared keywords: delete · exist

cursor
Community

principle-redesign-from-first-principles

Apply when integrating a new requirement into an existing design.

1h installs
3
GitHub stars
13.2K
Updated
Oct 20
1 Files
View skill details →

Why explore this: Development
Shared keywords: 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.

1h installs
1
GitHub stars
140.6K
Updated
Sep 30
Apache-2.04 Files
View skill details →

Why explore this: Development
Shared keywords: 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.

1h installs
1
GitHub stars
0
Updated
Oct 2
MIT2 Files
View skill details →

Why explore this: Development
Shared keywords: principle · instead · Apply

from this repository

More skills

All 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.

1h installs
1
GitHub stars
13
Updated
Oct 20
MIT2 Files
View skill details →
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.

1h installs
1
GitHub stars
13
Updated
Oct 20
MIT2 Files
View skill details →
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.

1h installs
1
GitHub stars
13
Updated
Oct 20
MIT2 Files
View skill details →
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.

1h installs
1
GitHub stars
13
Updated
Oct 20
MIT2 Files
View skill details →