GitHub Integration

Kommit's GitHub integration lets you connect an existing repository to a project. Once connected, Kommit ingests the codebase into its knowledge base — and the AI can reference real code when you're speccing features, detecting your tech stack, and generating your PRD.

How it works

1. You install the Kommit AI GitHub App on your GitHub account or organisation.
2. You grant access to one or more repositories.
3. On the canvas, you add a Repository node and connect it to your repo.
4. Kommit syncs the repository — filtering relevant files, chunking the code, and embedding it into the project's knowledge base.
5. The AI can now cite actual code in conversations and use it as context during PRD generation.

Installing the GitHub App

1. In any project, click the GitHub button in the canvas toolbar.
2. You'll be redirected to GitHub to install the Kommit AI GitHub App.
3. Choose whether to install on your personal account or an organisation.
4. Select All repositories or Only select repositories.
5. Click Install. You'll be redirected back to Kommit.

The app only requests the permissions it needs: read access to code, metadata, and repository structure. It does not request write access.

Adding a Repository node

1. Click Add node in the canvas toolbar.
2. Select Repository.
3. A Repository node appears on the canvas.
4. Open the node and click Connect repository.
5. Select the installation (your account or org) and then the specific repository.
6. Click Connect.

Syncing

After connecting, Kommit begins ingesting the repository in the background. The node shows a syncing spinner while this is in progress. Typical sync time is under 60 seconds for most codebases.

During ingestion, Kommit analyzes your codebase, extracts relevant code patterns, and makes them available as context for AI conversations and PRD generation.

Tech stack auto-detection: Kommit detects your tech stack from standard project configuration files automatically. If a Tech Stack node exists on your canvas, detected values are merged into its structured data.

Re-syncing

Click Re-sync on the Repository node to ingest the latest version of the repository. Re-syncing replaces the previous embeddings for that repo — it does not duplicate them.

Re-sync manually whenever you've made significant changes to the codebase that are relevant to the spec you're building.

Disconnecting a repository

Open the Repository node and click Disconnect. This removes the repository connection and deletes all embeddings for that repo from the knowledge base.

Disconnecting does not uninstall the GitHub App — you can reconnect the same repo at any time.

Uninstalling the GitHub App

To fully remove Kommit's access to GitHub:

1. Go to Settings in the Kommit dashboard.
2. Click Disconnect GitHub App.
3. Confirm the uninstall.

This revokes Kommit's access to all repositories and removes the app from your GitHub account. It also disconnects any active Repository nodes across all projects.

Using repo context in conversations

Once a repo is synced, the AI automatically retrieves relevant code excerpts during conversations. You do not need to reference the repo explicitly — the AI queries the knowledge base based on your message and injects the most relevant chunks as context.

When the AI uses retrieved code, it includes footnote citations in its response — for example [1] — that link directly to the source file on GitHub.

Using repo context in PRD generation

A toggle on the PRD generation panel — Include repository context — controls whether repo embeddings are used during PRD generation. Enable this when generating a PRD for features that build on your existing codebase.