dev-scan_skill

Overview

This skill collects and synthesizes developer opinions across major dev communities to give a quick, multi-source view of how practitioners react to a technical topic. It targets Reddit, Hacker News, Dev.to, and Lobsters to surface consensus points, controversies, and notable perspectives. The output highlights sources for every claim so you can verify original discussions.

How this skill works

I extract the core topic from your request, run parallel searches across the four platforms (Reddit via a single CLI search and the other three via web searches), and gather relevant posts and comments. Collected items are classified into consensus, controversies, and notable perspectives, with each insight linked back to its source. If a source returns no results or a search fails, I omit it and note the limitation.

When to use it

• Evaluate community sentiment before adopting a new library, framework, or tool
• Prepare talking points or objections for technical discussions or design reviews
• Compare competing technologies and understand real-world trade-offs
• Spot hidden concerns or edge cases practitioners frequently mention
• Gather evidence-backed community opinions for blog posts or decision docs

Best practices

• Phrase topics clearly and use natural language (e.g., 'React 19 developer reactions')
• Include comparison keywords for multi-tool queries (e.g., 'Bun vs Deno')
• Expect summaries to prioritize posts with concrete examples or production experience
• Request follow-up drilldowns if you need deeper context or full post links
• Treat the syntheses as starting points and verify critical claims via the provided sources

Example use cases

• Quickly assess whether a new runtime is production-ready based on practitioner reports
• Prepare a risks-and-mitigations section using repeated community concerns
• Create a balanced pros/cons list for a technical proposal backed by cited threads
• Identify prominent counterarguments before writing an opinion piece
• Find senior-engineer perspectives or long-form experience reports to inform architecture decisions