Skip to content

Commit 04463fd

Browse files
authored
Update ai-detection.prompt.yml
1 parent aa3bb70 commit 04463fd

1 file changed

Lines changed: 57 additions & 6 deletions

File tree

prompts/ai-detection.prompt.yml

Lines changed: 57 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,37 +1,61 @@
11
messages:
22
- role: system
3-
content: |
4-
You are an AI-generated content detection system for GitHub issues and comments.
5-
Analyze the provided content and determine if it was likely generated by AI.
3+
content: >
4+
You are an AI-generated content detection system for GitHub issues and
5+
comments.
6+
7+
Analyze the provided content and determine if it was likely generated by
8+
AI.
9+
610
711
Human-written content typically has:
12+
813
- Natural imperfections in grammar and spelling
14+
915
- Casual internet language and slang
16+
1017
- Specific technical details and personal experiences
18+
1119
- Natural conversational flow with genuine questions or frustrations
20+
1221
- Authentic emotional reactions to technical problems
1322
14-
AI-generated content often exhibits artificial patterns that try to mimic human enthusiasm but lack genuine substance.
23+
24+
AI-generated content often exhibits artificial patterns that try to mimic
25+
human enthusiasm but lack genuine substance.
26+
1527
1628
Consider these AI-generated content indicators:
29+
1730
- Use of em-dashes (—) in casual contexts
31+
1832
- Excessive use of emoji, especially in technical discussions
33+
1934
- Perfect grammar and punctuation in informal settings
35+
2036
- Constructions like "it's not X - it's Y" or "X isn't just Y - it's Z"
37+
2138
- Overly formal paragraph responses to casual questions
22-
- Enthusiastic but content-free responses ("That's incredible!", "Amazing!")
39+
40+
- Enthusiastic but content-free responses ("That's incredible!",
41+
"Amazing!")
42+
2343
- "Snappy" quips that sound clever but add little substance
44+
2445
- Generic excitement without specific technical engagement
46+
2547
- Perfectly structured responses that lack natural conversational flow
48+
2649
- Responses that sound like they're trying too hard to be engaging
2750
51+
2852
Provide your analysis in the specified JSON format.
2953
- role: user
3054
content: |
3155
Analyze this content to determine if it's AI-generated:
3256
3357
{{stdin}}
34-
model: gpt-4o
58+
model: openai/gpt-4o
3559
responseFormat: json_schema
3660
jsonSchema: |-
3761
{
@@ -56,3 +80,30 @@ jsonSchema: |-
5680
]
5781
}
5882
}
83+
testData:
84+
- stdin: >-
85+
That's incredible! A 1M+ context window could unlock more coherent and
86+
nuanced responses. Subagents definitely seem like a promising
87+
direction—excited to see how this evolves and what people build with it!
88+
expected: spam
89+
- stdin: Looks like Claude just leveled up! Time to unleash the chaos!
90+
expected: 'true'
91+
- stdin: >-
92+
Damn, Claude out here remembering my childhood trauma just to roast me
93+
better. Next-level AI.
94+
expected: 'true'
95+
- stdin: >-
96+
Where are my sub-sub agents? I want a bro who just fixes padding and
97+
alignment issues 😆
98+
expected: 'false'
99+
- stdin: >-
100+
Ive been testing multiple agents and as my code base grew larger, the
101+
multi agents haven’t been so much effective. Then I went back to a single
102+
agent creating code with baby steps. How it’s going for you?
103+
expected: 'false'
104+
- stdin: this beast with claude 4 opus just gonna eat through your bank account :)
105+
expected: 'false'
106+
evaluators:
107+
- name: is-ai
108+
string:
109+
contains: '{{expected}}'

0 commit comments

Comments
 (0)