10 GitHub Tricks for Faster, Smarter Devs

Just learned a pretty cool GitHub shortcut. When you’re inside any GitHub repo and press `>` on your keyboard, it instantly opens the repo in VS Code online. No cloning, no local setup, just a quick way to browse and edit code right in the browser. Small feature, but very useful. #github #shortcut #useful

GitHub's rolling out some neat updates to its standard code findings. Less noise, more signal when scanning those public repos. Definitely worth a look if you're building in the open. #CodeQuality #DevTools

GitHub doesn't tell you how big a repo actually is until you've already pulled it down. So you wait. You watch the progress bar. You wonder if you really needed all of it. Reposizer is a one-line npm tool that shows you the size, file count, language breakdown, and stars of any repo — public or private — before you clone.   npx reposizer owner/repo No login. No GitHub token unless the repo is private. It's the check I wish I'd had every time I've ever blindly typed git clone. 📘 Docs: https://lnkd.in/e4Zgs7EN #opensource #developertools #npm #buildInPublic

How much time is spent just setting up development environments? GitHub Codespaces seems like a useful way to cut down some of that friction. A few clear advantages: * less time spent on local setup * templates and preconfigured environments can keep things consistent * cloud-based so it's easily accessible Interesting tool to know.

GitHub is the main place where people save their code. They’re forecasting at 14 FOLD increase in code commits by the end of the year as a MINIMUM. cf last year.

I bet the next billion-dollar product is probably sitting in a private GitHub repo right now just a founder who keeps saying "it's not ready yet"

GitHub just rolled out a Rule insights dashboard and a unified filter bar! This is great for anyone managing repos with complex rule sets. Finally, a clearer view on how those rules are performing and easier filtering. Little quality-of-life updates like these make a big difference in daily dev work. #GitHub #DevTools

GitHub is on pace for 14 billion (!) commits this year. Up from one billion in 2025. GitHub's COO, Kyle Daigle, told The Information the platform now sees two hundred and seventy-five million commits a week and is hitting infrastructure limits. Claude Code alone is up twenty-five times in six months. I have been trying to find a historical comparison. Mass manufacturing is the closest I got, because that handed production to machines too. But quality control was easier there and involved statistical sampling on identical units. Code is not identical and every commit is bespoke. The obvious question is whether quality is keeping up? The less obvious one is whether anyone is even checking. My guess is most are not. Fourteen billion commits need fourteen billion answers to the same question. Did this produce any value?

GitHub introduced gh skill in the CLI, and it’s a small change with bigger implications than it looks. You can install, manage, and share agent skills straight from your terminal. These aren’t just predefined prompts. They package capabilities that can connect to tools, scripts, and workflows. So instead of telling an agent what to do every time, you start giving it reusable abilities it can execute. https://lnkd.in/eUCWWgec

I was telling my partners in crime Renato Ribeiro Frederico Santos and Eduardo Fernandes that skills were the invention of the century. Can't imagine my life without them anymore. This makes it so easy to discover, install, manage and publish them, right from your terminal.