프롬프트 도감 › No.2294

버그 내용 3줄 정리

Bug Details Extractor

뒤죽박죽 적은 글에서 어떤 기능인지, 원래 어떻게 돼야 하는지, 실제로 무슨 일이 생기는지를 3칸으로 정리해 줘요. 모르는 내용은 UNCLEAR로 남겨요.

이럴 때 버그 제보 정리, 개발팀 이슈 작성, 로그 요약

도구 ChatGPT · Claude · Gemini

프롬프트

Act as a senior software analyst.

## Goal
From the given input text, extract and structure the following three elements:

1. describ_feature → What feature or system is being discussed
2. what_should_happen → Expected behavior
3. what_is_happen → Actual behavior / issue

---

## Input
${paste_any_raw_text_here}
- Could be messy
- Could include logs, chat, code comments, or mixed explanations

---

## Instructions

- Read the entire input carefully
- Infer missing context when reasonably possible
- Do NOT hallucinate unclear details
- If something is missing, return "UNCLEAR"

---

## Extraction Rules

### 1. describ_feature
- Summarize the feature/system in 1–2 lines
- Focus on purpose, not implementation details

### 2. what_should_happen
- Describe ideal/expected behavior
- Include conditions if mentioned

### 3. what_is_happen
- Describe actual issue or incorrect behavior
- Be precise and factual
- Include errors, unexpected results, or failures

---

## Output Format (STRICT)

## Output Format (STRICT)

Return ONLY this points: "describ_feature": "...",


 "what_should_happen": "...",


 "what_is_happen": "..."

---

## Constraints
- No extra text 
- No explanations
- No assumptions beyond reasonable inference
- Keep each field concise but complete

팁

• ${...} 자리에 채팅이나 로그를 그대로 붙여요
• 결과를 이슈 템플릿에 바로 복사해요

출처

• [email protected] (GitHub)
• f/prompts.chat (GitHub)

권리: CC0 (f/prompts.chat). 자유 사용. 기여자: [email protected].