What happens when you build a GitHub CLI extension with Copilot CLI? P̶r̶o̶g̶r̶a̶m̶ ̶M̶a̶n̶a̶g̶e̶r̶ Dungeon Master Lee Reilly created one that turns your repo into a dungeon ... with procedurally generated levels and bugs that fight back. ⚔️ Here's how to enter the battle. ▶️

@leereilly Pretty interesting! I have something similar that I built too.

@leereilly 버그가 직접 공격까지 하면 이제 진짜 리포가 던전이네. 개발하다 지칠 때 한 번씩 돌려보면 정신 번쩍 들긴 하겠다.

@leereilly I'm not sure turning my repo into a game makes me want to fix bugs faster. If anything, I'd just avoid the scary files where all the dragons live. My finance app's auth folder would be final boss level and I'd never touch it again.

@leereilly Turning repos into games? That’s genius

@leereilly Excited about this. But when are we finally getting proper visibility into token/rate limits? Right now it’s unusable for me on the highest paid plan. I’ve already reported it in issues like #4280056 and #4178340, and there’s still no clear way to see limits, how to manage usage.

@leereilly CLI extensions are one of GitHub's most quietly useful surfaces. You can ship a micro tool that lives inside gh and distributes through the same auth you already have. Turning that into a roguelike is a very good abuse of the primitive.

@leereilly Fixed the rate-limit bug ?

@leereilly This is where AI CLIs get interesting. The opportunity is not “chat with your repo.” It is turning repo operations into executable loops: inspect → change → run → fail → patch → explain. That loop is where developer trust is either earned or destroyed.

@leereilly Hi GitHub your AI checker is rejecting my profile for no reason even though everything is right? Can have your team to help me out ?

@leereilly No customer support from Github for my enterprise members to sign up Github account. Please help!!!

@leereilly 버그가 몬스터로 나온다면 우리 레거시 코드는 최종보스급이겠네 ㅋ

@leereilly procedural bugs that fight back sounds like a fun way to stress test your ci pipeline before the real reviews hit

@leereilly I dont use copilot. Microsoft produces nothing. They take and they ruin.

@leereilly Turning your repo into a dungeon where bugs fight back is unironically the most accurate model of real world software.

@leereilly Yeah that kinda funny 🌝 but to be honest GitHub cli is still kinda complex I think I will start a project on my GitHub to make a one command that will init everything and another one command that will add commit and push, I know Vscode already solves this but it still laggy

@leereilly Imagine making a windows command line tool using copilot

@leereilly bugs hitting back fr tho my auth folder is eldritch horror level

@leereilly That’s actually so cool, turning bugs into enemies is genius

@leereilly This is the most delightfully unexpected use of Copilot CLI I’ve seen. Procedural dungeons, bugs that fight back now that’s the kind of creative dev loop we need more of PR approved.

@leereilly The real flex here isn't the dungeon — it's that CLI extensions are an underrated escape hatch from waiting for GitHub to ship the feature you actually need. Build your own surface. Most devs don't realize that's on the table.

@leereilly GitHub deserves more visibility Access to fast growing African tech ecosystems and a high ranking SEO article with search intent could boost that

@leereilly looks like angband

@leereilly ✊

@leereilly 300 new bugs 200 coding syntax errors 100 bugs on bugs Like seriously I don't know the difference between chatgpt and copilot