`rewriteIssue` Function Generates Incorrect and Verbose Outputs

kleneway commented 1 month ago

Description

The rewriteIssue function in the githubRouter TRPC route on the backend is malfunctioning by referencing nonexistent file names and producing overly verbose outputs. This leads to the generation of issues with inaccurate information and unnecessary details, hindering the development workflow.

Expected Behavior

The rewriteIssue function should generate issues that accurately reflect only the existing files in the system.
The output should be concise, containing relevant information without unnecessary verbosity.

Actual Behavior

The function references file names that do not exist in the system, indicating it is "hallucinating" file names.
The output includes excessive information about adding tests and other irrelevant data, making the issues unnecessarily wordy.

Additional Information

It is crucial to update the TRPC route to ensure that the rewriteIssue function:
- Uses only the actual file names from the codebase context to prevent hallucinations.
- Generates concise and precise issues that do not require user modification.
- Includes an overview of every file in the codebase to maintain consistency and accuracy in issue generation.

Proposed Solution

Refactor the rewriteIssue function to strictly reference existing files by passing codebase context with overviews of each file in the codebase.
Pass in the repo and org so the function can get the codebase context. See the evaluateIssue function in the githubRouter file to get an example of how that is done. Refactor that out into a shared function that can take a repoOwner, repoName, and accessToken, and return the codebase context for that project.
Update the prompt to simplify the output generation logic to eliminate unnecessary verbosity and ensure clarity in the issues produced.

@jacob-ai-bot --skip-build