GitHub Copilot isn’t just for completing code—if you feed it the right prompts, it can scan your pull requests, issues, and more to generate discussion ideas, outlines, and even full drafts of blogs. In other words, it can help you better showcase your work via discussions, writeups, etc.
Below, you’ll find a series of prompts designed to help you from brainstorming new topics to honing your final paragraphs. Note depending on the context/area in which you run this prompt, you might need to specify the repo or repos you want Copilot to analyze.
Prompts to get ideas for a Discussion/Blog
- Brainstorm Blog Angles from Recent PRs:
I’ve worked on three major PRs (#21, #27, and #44) in the last month. Could you suggest five potential blog topics that highlight the unique challenges or solutions from each PR? - Combine Issues and Code Changes:
We improved backend performance in PR #16 and addressed user feedback in Issues #10 and #12. What interesting blog ideas can you propose that tie these updates together for a developer audience? - Major Version Upgrade Inspiration:
We released a major version upgrade in PR #99 for our library. Could you suggest three blog angles that highlight the major changes, the lessons we learned, and how the community can benefit from it? - Feature-Focused Topic Generation:
We’ve been working on a new AI-driven feature in PR #120. Please propose some blog post titles and short descriptions that will catch developers’ attention while explaining how this feature fits into our product roadmap. - Implementation Deep Dive:
I just finished implementing a complex authentication flow in PR #30. Could you outline a blog post explaining the challenges we faced, the approach we took to solve them, and a brief code example highlighting key sections? - Lessons Learned & Best Practices:
Please suggest a blog post structure that covers the top five lessons learned from our recent microservices refactor in PR #78. Include any best practices for error handling, testing, and deployment. - Architecture & Design Decisions:
Generate a blog outline that discusses our shift to a more modular architecture in PR #55. I want to explain why we made the switch, how it impacts scalability, and any trade-offs we faced along the way. - Code Example Showcase:
Propose a developer-focused blog post centered on the new caching mechanism we built in PR #64. Highlight the major code snippets, performance improvements, and any pitfalls or debugging tips for others who want to implement similar functionality.
Prompts to draft a Discussion/Blog
- Prompt for an Outline Based on PRs and Issues:
Check out PR #42 and PR #53 in our repo. Could you propose an outline for a blog post that introduces the new features from those PRs, mentions any user-facing improvements, and wrap up with next steps? - Prompt for a Full Draft with Specific Focus:
Please write a short blog post describing how we integrated a new logging module from PR #22, fixed major bugs in Issues #15 and #16, and introduced a better error-handling feature. Make sure to include the main benefits to the community. - Prompt to Summarize Commit History:
I want a blog section that summarizes the last five commits, highlighting any major changes or exciting features. Could you draft a paragraph focusing on what changed and why it matters? - Prompt for a Highlight of Collaborators:
Generate a brief ‘shout-out’ paragraph that highlights the contributors who submitted PRs #33 and #37, explaining their impact and thanking them for their work. - Prompt for Creating a Feature-Focused Section:
Create a blog subsection that introduces our brand-new feature (from PR #41) in plain language for non-technical readers. Mention how it solves a pain point and include a quick code snippet if helpful. - Prompt to Refine Tone & Style:
Please rewrite the conclusion in a more informal, conversational style. The original conclusion was: ‘Our team successfully launched a groundbreaking update.’ Make it feel more personal and celebratory. - Prompt for Next Steps & Roadmap:
Draft a final section on upcoming milestones and open issues labeled ‘enhancement.’ Show how these tie into our long-term roadmap and why readers should stay tuned.