dev-scan

Dev Opinions Scan

Collect and synthesize diverse opinions on a specific topic from multiple developer communities.

Purpose

On technical topics, diverse perspectivesquickly identify:

• Distribution of pros and cons
• Practitioners' experiences
• Hidden concerns or advantages
• Unique or noteworthy perspectives

Data Sources

Platform	Method
Reddit	Gemini CLI
Hacker News	WebSearch
Dev.to	WebSearch
Lobsters	WebSearch

Execution

Step 1: Topic Extraction

Extract the core topic from the user request.

Example:

• "Developer reactions to React 19" → React 19
• "Bun vs Deno community opinions" → Bun vs Deno

Step 2: Parallel Search (Single Message, 4 Sources)

Reddit (Gemini CLI - WebFetch blocked):

# 단일 Gemini 호출로 Reddit 검색 (명시적 검색 지시 필수)
gemini -p "Search Reddit for discussions about {TOPIC}. Summarize the main opinions, debates, and insights from developers. Include Reddit post URLs where possible. Focus on: 1) Common opinions 2) Controversies 3) Notable perspectives from experienced developers."

Cautions:

• site:reddit.com The format does not work - Gemini interprets it as a task request rather than a search query
• An explicit search instruction in the form "Search Reddit for..." is required
• A single call is more stable than parallel calls (prevents mixed output)

Other Sources (WebSearch, parallel):

WebSearch: "{topic} site:news.ycombinator.com"
WebSearch: "{topic} site:dev.to"
WebSearch: "{topic} site:lobste.rs"

CRITICAL: The 4 searches must be in one messageexecuted in parallel. Gemini uses a single call, WebSearch uses 3 in parallel.

Step 3: Synthesize & Present

Analyze the collected data to derive meaningful insights.

3-1. Opinion classification and pattern identification

Classify the opinions collected from each source according to the following criteria:

• Support/positive: Opinions supporting the technology/tool
• Opposition/negative: Concerns, criticism, alternative proposals
• Neutral/conditional: Conditional opinions such as "only if...", "if used with..."
• Experience-based: Opinions based on actual production usage experience

3-2. Deriving consensus

Across multiple communities, repeatedly appearing identify opinions:

• If the same point is mentioned in 2 or more sources, classify it as a consensus
• Opinions mentioned simultaneously on Reddit and HN in particular have high credibility
• Prioritize opinions that include specific figures or examples
• At least 5 or more consensus points derivation goal

3-3. Identifying controversy

Between communities or within a community, opinions diverge identify points:

• When opposing opinions exist on the same topic
• Threads where active discussion took place in the comments
• Topics with many counterarguments such as "depends on...", "but actually..."
• At least 3 or more controversy points identification goal

3-4. Selecting notable perspectives

Discover unique or in-depth insights:

• Opinions that differ from the majority but have solid logical grounding
• Opinions of senior developers or experts in the field
• Insights from actual large-scale project experience
• Edge cases or long-term perspectives that others tend to miss
• At least 3 noteworthy perspectives Selection goal

Output Format

Core principles: Attach sources inline to every opinion. Do not include opinions without sources.

## Key Insights

### Consensus (공통 의견)

1. **[의견 제목]**
   - [구체적인 내용 설명]
   - [추가 맥락이나 예시]
   - Sources: [Reddit](url), [HN](url)

2. **[의견 제목]**
   - [구체적인 내용]
   - Source: [Dev.to](url)

(최소 5개 이상)

---

### Controversy (논쟁점)

1. **[논쟁 주제]**
   - 찬성측: "[인용]" - [Source](url)
   - 반대측: "[인용]" - [Source](url)
   - 맥락: [왜 의견이 갈리는지]

2. **[논쟁 주제]**
   - ...

(최소 3개 이상)

---

### Notable Perspective (주목할 시각)

1. **[인사이트 제목]**
   > "[원문 인용 또는 핵심 문장]"
   - [왜 주목할 만한지 설명]
   - Source: [Platform](url)

2. **[인사이트 제목]**
   - ...

(최소 3개 이상)

Source citation rules

• Inline links required: At the end of every opinion, in the format Source: [Platform](url) attach in the format
• Multiple sources: If the same opinion is mentioned in multiple places, Sources: [Reddit](url), [HN](url)
• Direct quotes: When possible, quote the original text in the form "..." quote in the form
• URL accuracy: Include only actually accessible links (URLs confirmed in search results)

Error Handling

Situation	Response
No search results	Omit that platform, focus on other sources
Gemini CLI failure	Omit Reddit and proceed with the remaining 3
Topic is too new	Notify of insufficient results, suggest related keywords

Examples

Simple topic:

User: "Tailwind v4 개발자들 반응 어때?"
→ topic: "Tailwind v4"
→ 4개 소스 병렬 검색
→ 종합 인사이트 제공

Comparison topic:

User: "pnpm vs yarn vs npm 커뮤니티 의견"
→ topic: "pnpm vs yarn vs npm comparison"
→ 4개 소스 병렬 검색
→ 각 도구별 선호도 정리

Controversial topic:

User: "Claude Code Plugin 에 대한 개발자들 생각"
→ topic: "Claude Code Plugin tips"
→ 4개 소스 병렬 검색
→ 종합 인사이트 제공