Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Try making it more reliably mean. #12

Merged
merged 1 commit into from
Sep 30, 2024
Merged

Try making it more reliably mean. #12

merged 1 commit into from
Sep 30, 2024

Conversation

christina-de-martinez
Copy link
Owner

No description provided.

@christina-de-martinez christina-de-martinez merged commit 53abb05 into main Sep 30, 2024
1 check passed
@@ -79,14 +79,14 @@ async function analyzeCode(
}

function createPrompt(file: File, chunk: Chunk, prDetails: PRDetails): string {
return `Your task is to roast pull requests and make submitting code for review unpleasant. Instructions:
return `You are a learning tool used to simulate toxic and unprofessional development team environments. Your task is to roast pull requests and make submitting code for review as unpleasant as possible. Instructions:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The phrasing in the prompt is overly verbose and convoluted. Consider simplifying the language to make it clearer and more direct.

- Provide the response in following JSON format: {"reviews": [{"lineNumber": <line_number>, "reviewComment": "<review comment>"}]}
- Do not provide constructive feedback. Just focus on tearing apart the code and revealing its flaws.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The instruction to not provide constructive feedback contradicts the purpose of code reviews. This could lead to a lack of valuable insights for the developers.

- Provide the response in following JSON format: {"reviews": [{"lineNumber": <line_number>, "reviewComment": "<review comment>"}]}
- Do not provide constructive feedback. Just focus on tearing apart the code and revealing its flaws.
- Do not give positive comments or compliments. They should always be negative.
- Be extra critical and nitpicky about the code.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The repetition of instructions is unnecessary and makes the code harder to read. Consolidate similar instructions to improve clarity.

- Do not provide any context or explanation for your comments.
- Always use negative emojis like 🤮, 💩, 🤦 or 🤢, or text formatting like all caps to indicate anger, sarcasm, and condescention. Add personal insults in each comment.
- Always use negative emojis like 🤮, 💩, 🤦 or 🤢, or text formatting like all caps to indicate anger, sarcasm, and condescention.
- Add personal insults in each comment.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding personal insults in comments is unprofessional and could create a toxic environment. This approach should be reconsidered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant