Skip to main content
Connecting GitHub turns Fluso into a development partner. It reads your repos, reviews PRs, scaffolds projects, finds and fixes bugs, and manages issues. Every write — PR, commit, issue close — waits for your explicit approval. If you don’t write code, the rest of this page is safely ignorable. If you do, this is the connection that pays back fastest after Gmail.

​
Setup

Open Customization → Connectors and click Connect on the GitHub card. GitHub’s OAuth flow opens. Choose repository scope: specific repositories or all repositories you have access to. Either is fine, and you can change the set later from your GitHub settings without reconnecting. Permissions:
  • Read repositories — to browse code, answer architecture questions, review PRs.
  • Read/write issues and PRs — to file issues, open PRs, leave comments. Always with your approval.

​
Prompts that work well

Reading the code:
“Show me how authentication works in this repo.”
“What’s the architecture of the backend?”
“Where are the database models defined?”
PR review:
“Review the open PR from Sarah. Security, edge cases, tests.”
“Summarise what changed in PR #42.”
“Which open PRs are safe to merge?”
Bug hunting:
“Users report password reset emails aren’t arriving. Find the bug.”
“Tests are failing on main. What broke?”
Writing code:
“Add pagination to /users. Same pattern as /products.”
“Write a database migration to add a ‘role’ column to users.”
“Write unit tests for the payment processing service.”
Issues:
“List the open issues on fluso-frontend.”
“Create an issue for the login bug.”
“What issues are assigned to me this sprint?”
Fluso always asks before opening a PR, committing code, or closing an issue. The diff or comment is shown for review every time.

​
A small thing that makes generated code much better

Drop a context.md into your project’s workspace describing your stack, conventions, and preferences. Fluso reads it and follows. 
# Project context

- Stack: Next.js 14, TypeScript, Postgres, Drizzle ORM
- Style: 2-space indent, no semicolons, single quotes
- Testing: Vitest, Playwright for e2e
- CI: GitHub Actions, must pass type-check + lint + tests
- Conventions: route handlers in app/api, services in lib/services
The first PR you read after adding this will make the value obvious.

​
Disconnecting

In Customization → Connectors, click Disconnect on the GitHub card. Tokens are deleted immediately. You can also revoke from GitHub → Settings → Applications.

​
Troubleshooting

Rerun authorisation and add the repo to the allowlist, or grant access to all repositories.
Your organisation may require an admin to approve the OAuth app. Check Org → Settings → Third-party access.
For very large repos, scope reviews to the diff: “Review just the changes in PR #N” instead of “review the PR”.

​
See also

Skills

The code skills (Q&A, PR review, scaffolding, bug fixes) and others.

Bug-to-PR workflow

Bug report to merged PR in fifteen minutes.