/evaluate and /review option for brownfield.

[wetware0]

I thought it would be cool to have a few options for brownfield situations.

Add the following commands:

• /evaluate to traverse the code and evaluate the code quality against the constitution.
  Either output to a markdown, or prepare a specify, plan, or task entry to correct the anomalies.

• /review that accepts an argument of a GitHub PR URL or #. Which reviews the code change in the PR using the rules defined in the constitution for quality anomalies. If the anomalies are found, output or returned in a GitHub review comment. Or if none are found, optionally accept the PR for merge.

[jeffreybarron]

I’d like to add that it would be awesome to recurse through the entire codebase, infer the meaning and intention of each block of code, and reverse-engineer a complete specification or constitution. From there, plans could be written to rewrite the legacy code based on the inferred intentions, using a new language or framework—for example, migrating from Next.js to Spring Boot, or vice versa.

I have watched https://youtu.be/SGHIQTsPzuY?si=Zh7zjnidZDdO_ZFX and I see how that goes along way, but it does require existing knoweldge of the code base and functional requirements. I am talking about a true vide coded forklift re-write feature.

essentially an automated tool that could analyse code at scale, extract the intent, and then regenerate the system in another stack without relying on legacy documentation or tribal knowledge.