GitHub DeepWiki Button
https://github.com/yamadashy/github-deepwiki-button- Category
- Developer Tools
- Rank
- No. 1407Tools index
Previous survey · No. 1412 ·
- Pricing
- Open Source
- Type
- TOOL
- Builder
- yamadashy
- GitHub
- 99 stars
- Date
About
Browser extension that adds a DeepWiki button to quickly access DeepWiki from GitHub repositories.
What it does
While viewing a GitHub repository, it creates a direct link using the repository owner and name. The destination opens in a new tab, where DeepWiki provides generated documentation and chat.
Why it's ranked here
This is a focused convenience tool with readable, compact behavior and support for three major browsers. Its value depends entirely on frequent GitHub-to-DeepWiki handoffs, but it removes a small, repeated URL-editing task.
What's good
The link uses only the repository coordinates already present in the current URL. It opens with protections against access to the originating page. The extension also watches GitHub’s dynamic navigation and restores its control when repository pages change without a full reload.
Tradeoffs
It does not generate, validate, or cache documentation itself. DeepWiki remains an external dependency. Its placement relies on specific GitHub navigation elements, so GitHub markup changes could break the control. The extension requests access across GitHub pages, although its privacy policy says it collects no data.
How to use it well
It suits developers who repeatedly inspect unfamiliar public repositories and already use DeepWiki for orientation or questions. Keep it as a navigation shortcut during repository triage. It does not replace source reading, documentation quality checks, private-repository tooling, or a general GitHub productivity suite.
Technical notes+
app/scripts/content.ts extracts the first two URL path segments, builds a deepwiki.com link, inserts it into GitHub’s repository action list, and uses a MutationObserver for SPA navigation. app/scripts/background.ts applies declared CSS and JavaScript to eligible open GitHub tabs while treating failures as nonfatal. app/manifest.json uses Manifest V3, the scripting permission, and a GitHub host permission, with Firefox-specific background and minimum-version settings. package.json builds through WebExtension Toolbox and checks Biome, TypeScript, and secrets. Development runtime guidance conflicts: README.md says Node.js 22 or higher, package.json requires at least 24.0.1, while .node-version and .tool-versions specify 23.6.0.
Observed
- License
- MIT
- Primary language
- TypeScript
- Interface
- Manifest V3 browser extension
- Install surface
- Chrome Web Store, Firefox Add-ons, and Microsoft Edge Addons
- Platform support
- Chrome, Firefox, and Edge builds are documented
- Permissions
- Uses the scripting permission and host access for https://github.com/*
- Build tooling
- WebExtension Toolbox with npm scripts for browser-specific development and builds
Read from README.md, package.json, scripts/generate-icons.ts, app/scripts/content.ts, app/scripts/background.ts, LICENSE, biome.json, .node-version, tsconfig.json, .tool-versions, secretlintrc.json, .secretlintrc.json, app/manifest.json, .github/FUNDING.yml, .github/renovate.json5.
What it can do
Add DeepWiki button to GitHub repository pages
GitHub repository page → DeepWiki access button in browser
Navigate from GitHub repository to DeepWiki
Click on DeepWiki button → DeepWiki page for the repository
Integrate DeepWiki functionality into GitHub workflow
GitHub repository browsing session → Enhanced GitHub interface with DeepWiki access
Provide quick access to repository documentation analysis
GitHub repository → Direct link to DeepWiki analysis of repository
Tags
Tech Stack
Media
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.