This is a submission for the GitHub Copilot CLI Challenge
What I Built
What if your linter could actually fix the problems it found?
T...
For further actions, you may consider blocking this person and/or reporting abuse
For anyone curious about the Copilot CLI integration: the key discovery was
copilot --prompt "..." --allow-all-tools. The--promptflag runs it non-interactively, and--allow-all-toolsauto-approves file edits. Without these two flags, programmatic invocation wouldn't be possible. Happy to share more about the prompt engineering approach if anyone's interested.good work
good problem solver
Great Work!!
thanks
How is this different from eslint-plugin-jsx-a11y ?
eslint-plugin-jsx-a11y is excellent and covers similar ground for React projects.
key difference is:
Think of it as "what if your linter had an AI pair programmer attached."
Great idea. productivity win 🙌
thanks
Very cool!
Accessibility always matter. Great work 👏
This is seriously impressive. I recently ran an accessibility scan on one of my tool pages and fixing issues manually took hours — especially replacing clickable divs and adding proper labels. The idea of auto-fix with context-aware refactoring is a huge time saver. Curious — did you notice any cases where Copilot’s fix needed manual correction, or was it reliable most of the time?
nice terminal ui
Thanks, the terminal output uses chalk, gradient-string, and boxen.
good work safvan
This is seriously impressive 👏🔥
Nice work!😄