What if GitHub Copilot didn’t just help you write code but judged you for it?
What I Built
I had been waiting for a challenge that truly sounded like me for a long time, and that’s when the GitHub Copilot CLI Challenge showed up.
Within five minutes, the idea that popped into my head was to use Copilot CLI to do something with Copilot itself.
That’s when the idea of roasting the user for their GitHub Copilot usage came up.
Then I started wondering how to implement it.
Whether to build something that runs in the terminal but that would consume RAM.
Should I try a different approach?
That’s when the idea of a VS Code extension popped up (GitHub CLI actually helped me there ).
This was my first time using an AI pair programmer to help me build a project completely, because I had never built, or even thought about creating a VS Code extension before.
The roasts are static for now and don’t use AI, because I couldn’t afford an API key .
Demo
Click the following link:
Copilot Roaster Extension
Install the extension using the link.
And your setup is complete.
Then, open any sample file to test it.
Ask GitHub Copilot to write something and accept its suggestion to see the magic ✨
Find my demo below:
Demo
You can find the GitHub repository here.
Feel free to fork, modify, and upgrade it.
My Experience with GitHub Copilot CLI
<!-- Explain how you used GitHub Copilot CLI while building your project and how it impacted your development experience. -->
This was my first time using an AI pair programmer in the CLI. I was really excited to see how it worked. After installing it and typing copilot in the terminal, it felt like magic when this showed up.
I started wondering how it would work, which subscription it would use and which profile it would be linked to.
While thinking about all this, I typed a prompt, and that’s when I got an error saying I needed to log in to proceed further.
First, we need to use /login to sign in with our GitHub account.
After that, everything was smooth. The suggestions were almost exactly what I expected (maybe my prompt was too good ).
Then I tweaked things a bit, and tadaaa
The extension was ready and looked cool.
I added a few more roasts just to make sure the same ones didn’t repeat.
Then I published it on the Marketplace.
GitHub Copilot CLI provided me with the exact steps to publish the extension, because I had no clue how to do it and the whole process was smooth as well.
So go ahead, install the extension, let Copilot write your code, and brace yourself… because this time, you’re the one getting reviewed
Follow me on Linkedin | GitHub | Twitter
Subscribe to my newsletter and get articles delivered straight to your inbox.