Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.airglow.cc/llms.txt

Use this file to discover all available pages before exploring further.

GitHub QA app rendering a DeepWiki overlay with overview and relevant source files on a GitHub repository page
Ask a repo question and get an answer grounded in visible context.
  • Page · GitHub repo
  • Action · Answer a repo question
  • Result · Short answer with file context

​
The problem

Ask without leaving GitHub. You are on a repo page and need a quick answer without cloning the project or switching tools.

​
The prompt

A natural prompt for your coding agent: 
Build a GitHub app for the repo page I am viewing.
Let me ask a question and answer from the visible README, file, PR, or issue context.
If the page does not contain enough info, say what I should open next.

​
Iterations

1

First pass

Build a GitHub repo app. Let me type a question about the repo I'm
looking at and answer from whatever's visible on the page.
2

Show me what it's based on

Add a "based on:" line under each answer pointing at the source —
"README §2", "CHANGELOG.md", "PR #481 comment by alice". So I can
audit before I trust it.
3

Use file contents on file pages

When I'm viewing a specific file (or a PR diff, or an issue body),
use that content not just the page title. Right now on a file page
you're answering from the breadcrumb.
4

Prefer README on the repo root

On the repo root page, prefer the README over the sidebar metadata.
Only fall through to file tree or activity if the README doesn't
cover the question.
5

Don't fight GitHub's UI

Put the answer chip below GitHub's "About" widget on the right
rail, not over it. Don't change any GitHub styling, don't intercept
clicks on repo links.
6

Plug into DeepWiki for repo-wide context

The visible-page approach hits a wall fast — "how is auth handled"
needs the whole repo, not just what's on screen. Plug into DeepWiki
for the current repo so the answer can use real repo-wide context.
Keep the "based on:" line pointing at the actual files DeepWiki
references.

​
Result

  • The user asks a repo question from the GitHub page.
  • The answer stays short and points back to visible context.
  • Missing context produces a useful next step instead of a fake answer.
  • No GitHub state changes.

​
Try it

Install Airglow

Clone the SDK repo and load the Chrome extension.

View source

Browse the GitHub QA app under airglow-apps/github-qa/.