GitHub Secrets: Everything Hiding Behind One URL
Every trick here works on any public repo, costs nothing, and needs no install. Three of them are in the video. The rest are the ones I actually use every week. Open any repository and follow along.
1. Swap github.com for gitdiagram.com
Take any repo URL and change the domain. Nothing else.
github.com/owner/repo becomes gitdiagram.com/owner/repo
You get the entire codebase drawn as an architecture diagram. Every module, every file, and arrows showing what calls what. GitDiagram builds it from the source, so it matches the code rather than whatever the README claims.
This is the fastest way to understand a repo you have never opened. Two seconds instead of an hour of clicking through folders.
2. Swap it for gitingest.com
Same move, different domain.
github.com/owner/repo becomes gitingest.com/owner/repo
GitIngest flattens the whole repo into one text file your AI can actually read. You get a summary, the directory structure, and the full file contents, with a Copy all button and a Download button.
Now you paste that into Claude or ChatGPT and ask questions about the real code instead of describing it from memory. This is the single biggest upgrade to working on unfamiliar code with an agent.
3. Press the period key
Open any repo on GitHub and tap . on your keyboard.
VS Code opens in your browser, loaded with that repository. No clone, no install, no local setup. It runs at github.dev.
From there you get the real editor. The file tree, full text search across the repo, multi-file editing, and you can install extensions into the browser editor.
No keyboard handy, or the shortcut gets swallowed by your browser? Swap the domain to github1s.com/owner/repo and you land in the same place.
4. Swap it for deepwiki.com
github.com/owner/repo becomes deepwiki.com/owner/repo
DeepWiki reads the repository and writes it a full wiki. Architecture pages, how the parts connect, and a question box you can ask about the code.
Use this when the project has no documentation, which is most of them. You get the explanation the maintainer never wrote.
5. Swap it for gitmcp.io and your agent gets the repo
This is the one almost nobody knows.
github.com/owner/repo becomes gitmcp.io/owner/repo
GitMCP turns that repository into a live MCP server. Point Claude, Cursor, Windsurf or VS Code at the URL and your agent can query the repo directly, pulling the README, the docs and the source on demand.
The difference from GitIngest matters. GitIngest gives you one frozen snapshot to paste. GitMCP gives your agent a connection it can keep asking, so it fetches what it needs instead of you guessing what to include.
Add it to your MCP config like any other server.
{
"mcpServers": {
"repo-docs": {
"url": "https://gitmcp.io/OWNER/REPO"
}
}
}6. The URL suffixes nobody uses
These are built into GitHub. Add them to the end of a URL you already have.
See a markdown file's real source. Add ?plain=1 to any .md file URL. You get the raw markdown with line numbers instead of the rendered page, which is how you copy a README's exact formatting.
Get any commit as a patch. Add .patch or .diff to a commit URL. You get the plain-text change, ready to read or apply, with no API and no login.
Compare any two branches or tags. Use github.com/owner/repo/compare/v1...v2. Swap in any two branches, tags or commits and GitHub builds the full diff.
Download without cloning. Use github.com/owner/repo/archive/refs/heads/main.zip and the whole repo comes down as a zip.
Grab anyone's avatar. Add .png to a profile URL, so github.com/octocat.png returns the image file itself.
7. Five keyboard shortcuts that change how fast you move
Open a repo and use these. They are GitHub's own, straight from the docs.
t opens the file finder. Start typing a filename and jump straight to it. This replaces all folder clicking.
y rewrites the URL you are on into its permanent commit-pinned form. Share that version instead, and the line you pointed at still says the same thing next year.
b opens blame view on the file you are reading, so you see who changed each line and when.
l jumps to a line number.
? shows every shortcut GitHub has, on any page.
The y one is the one to build a habit around. A normal GitHub link rots the moment somebody edits the file.
Which one to use when
All of these solve different problems, so here is the short version.
New repo you have never seen, and you want the shape of it: gitdiagram.
You want to ask an AI about the code once: gitingest.
You want your agent to keep querying it while you work: gitmcp.
The project has no docs: deepwiki.
You want to actually edit something right now: press period.
Start with the period key. It is the one that changes your daily habits, and it has been sitting in GitHub the whole time.
If you want more in this direction, here is my animated GitHub profile build and the Claude Code skills I actually run.
Get the next one first
New prompts every week.
Free. The new drops and the tools behind them, before they hit the feed.
No spam · New issues Sunday · Unsubscribe anytime
Hire me for your business
Ready to invest in a custom build?
Implementation and custom builds start at $5,000 USD. Bring a specific business problem and an approved budget. Learning on your own? Keep exploring the free guides or join the community above.
Related guides
Guide
Turn Your GitHub Profile Into an Animated Terminal (No Widgets, No Tokens)
A matrix-rain contribution graph, a neofetch card, and your favorite meme, all animated, all files you own, refreshing themselves every day for free.
Guide
The 5 Free Claude Code Skills That Make Your Front End Stop Looking Vibe Coded
Anthropic's own design skill, Hallmark's 57 slop checks, Vercel's guidelines, 10,000 pre-built components and a browser Claude can see through. Every install command on one page.
Guide
My ChatGPT and Codex Plugin Setup (The Plugins + Copy-Paste Prompts)
The setup behind my video: browser control, computer use and image generation, with prompts you can use right now.
Guide
Never Hit a Claude Code Limit Again (Free OmniRoute Setup)
One free gateway connects Claude Code to 350+ AI providers, so the second you hit your session limit it keeps going on someone else's free tokens.
Frequently asked questions
The GitHub-native ones do, because you are already signed in. That covers the period key, ?plain=1, .patch, /compare, the archive download and every keyboard shortcut. The third-party swaps (GitDiagram, GitIngest, DeepWiki, GitMCP) read public repos, so a private one needs you to authorize access with that service first.
No. Every trick on this page works with no account and no payment on public repos. Some of the third-party tools offer paid tiers for heavier use or private access, but nothing here requires one.
GitIngest hands you a single text snapshot to paste into a chat. GitMCP gives your agent a live connection it can query again and again while it works. Use GitIngest for a one-off question and GitMCP when you are building against the repo.
It works on any repository page on GitHub in a desktop browser. If nothing happens, your cursor is probably inside a text box or your browser grabbed the key first. Use github1s.com/owner/repo instead and you get the same editor.
Yes. github.dev is real VS Code with GitHub's source control built in, so you can change files, stage them and commit straight back to a branch. It has no terminal and runs nothing, so it is for edits and reading, not for running the project.