Start with the repository, not another prompt
Bring the repository, the failing behaviour, your supported environment and a short backlog. Record which parts already work. A cleanup task needs a stable starting point so that an apparent improvement does not silently break an unrelated journey.
List the access an implementer needs and prefer a disposable environment with synthetic data. Keep production credentials out of prompts and issue descriptions. Identify who can approve changes and who owns the final release.
Turn cleanup into a bounded change
Replace “make the app production-ready” with a specific outcome, such as preventing one tenant from reading another tenant’s records. Define the failing example, the expected denial and the unaffected happy path before implementation.
Agree exclusions as well as acceptance checks. A missing billing architecture, data migration or continuous operations service is a separate scope decision. A fixed-duration sprint does not establish that every risk in an arbitrary prototype has been removed.
Accept evidence with the patch
Ask for the final diff, test output, review findings and a rollback note tied to the candidate commit. Check that the tests exercise the defect rather than simply mock the faulty function.
Getzilla provides an open source repository workflow. Review its current access and pricing on the home page. Confirm delivery scope separately; this draft does not create a service commitment or guarantee a production release.
Working sheet
| Observed problem | Acceptance check | Keep outside this task |
|---|---|---|
| Cross-tenant record access | Tenant B cannot read tenant A fixture | Redesign the entire identity provider |
| Payment callback runs twice | Duplicate fixture produces one logical update | Replace the payment provider |
| Generated test has no assertion | Wrong result makes the test fail | Maximise line coverage |
| One module repeats validation | Recorded valid and invalid inputs stay unchanged | Rewrite every module |
Questions about vibe coding cleanup services
Can cleanup rescue any prototype?
That depends on the repository, the missing capabilities and the agreed scope. A discovery pass can distinguish small repairs from work that requires a wider design or rebuild.
Does a green test suite mean the app is secure?
No. Tests establish the cases they actually exercise. Permission boundaries, secrets, dependencies and operational controls need their own evidence and review.
How should I use the working sheet?
Download the CSV and replace the sample rows with evidence from your repository. Record a clear acceptance check and an owner for each item. Keep unresolved assumptions visible rather than treating the example as a completed assessment.
Sources and further reading
Examples are illustrative. They are not customer results, security guarantees, or a substitute for checking the documentation for your installed version.
