Codebase Singularity

Quick start

1. Collect inputs: repo path, goal, constraints, risk tolerance, and validation commands.
2. Summarize: explain repo shape and where the change belongs; ask questions if ambiguous.
3. Plan: write a short plan with success criteria and validation steps.
4. Change: implement the smallest viable patch; avoid unrelated refactors.
5. Validate: run the requested command(s) or the closest available; record results.
6. Wrap up: report changes, evidence, risks, and next steps.

Inputs

• Repo path and task goal.
• Constraints (files to avoid, time or risk limits, API stability).
• Validation commands (tests, lint, build, or targeted checks).