PromptVaultRetire legacy code with evidence-backed checks
For engineers preparing a safe removal with a repository-specific verification artefact.
Works with
- Cursor
- GitHub Copilot
The prompt52 words · 2 blanks
What you fill in
- Removal brief
[removal_brief]ExampleRemove the v1 invoice renderer after all tenants move to the template service - Repository evidence
[repository_evidence]ExampleDirectory tree, search results, build scripts, deployment config, and relevant call sites
How to use it
- 1Open it in PromptVault. Find it in Coding, or search for “Retire legacy code with evidence-backed checks”.
- 2Fill in the 2 blanks. removal brief and repository evidence — the only things the prompt cannot know.
- 3Copy and paste it into Cursor. It also works with GitHub Copilot.
About this prompt
“Retire legacy code with evidence-backed checks” is a intermediate coding prompt. For engineers preparing a safe removal with a repository-specific verification artefact. It is 52 words long and written to get a usable answer on the first message, in Cursor and GitHub Copilot or any other chat assistant. Good for: checklist, legacy code, code review, testing and quick win. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.
More coding prompts
All 120 in Coding
A review checklist for time-sensitive codeFor engineers checking date and clock logic; returns proof-oriented review checks.- Prove duplicate suppression under concurrent requestsFor engineers adding a focused regression test directly inside an existing repository.
- A manual smoke test from a feature briefFor developers who need a compact, repeatable check before handing a feature to QA.
- A minimal failing test that isolates the defectFor developers turning a bug brief into a small, deterministic regression test.
- A pull request template for risky query changesFor teams that want query evidence and rollback details before database review.
- Collapse flag combinations into an explicit state machineFor engineers replacing scattered status checks with enforceable transitions and exhaustive tests.