GitHub, Linear, and Reviews
Start work from issues, PRs, workflows, security alerts, advisories, and Linear tickets.
Jean is strongest when work starts from real repository context instead of a blank chat box.
That is where the GitHub and Linear flows come in.
Start from GitHub context
When you create a new session for a project, Jean can start from:
- GitHub issues
- pull requests
- workflow runs
- security alerts
- security advisories
- existing branches
For many of these, Jean can create the worktree and immediately launch the matching investigation flow.
Mr. Robot issue sweeps
Mr. Robot is a beta project setting for automated GitHub issue sweeps. When enabled, Jean periodically checks open issues, applies included and excluded label filters, respects the project's active-hours window, and creates focused worktrees up to the configured run and active-worktree limits.
Each sweep can ask the selected planning backend/model to investigate and draft a plan. If you enable optional yolo execution, Jean can also approve ready plans automatically with the configured yolo backend/model. Mr. Robot worktrees are grouped separately on the project canvas so they do not crowd the regular Issues view.
Start from Linear
If you add a Linear API key, Jean can list and search Linear issues for the project.
That gives you a path from ticket to worktree to session without copying the issue into the prompt by hand.
GitHub dashboard
Jean also includes a cross-project GitHub dashboard so you can inspect issues, PRs, workflows, and security work across repositories from one place.
This is especially useful when you are juggling multiple repos and want one queue instead of five browser tabs.
PR review workflows
Jean supports several review-oriented flows:
- investigate a PR
- review code changes
- address inline PR comments
- open or update a PR
- merge a PR
Because the workspace is already branch-aware, review flows stay close to the actual diff and terminal state.
Security investigation
Jean can also start work from:
- Dependabot alerts
- repository security advisories
Those flows are useful when you need to answer questions like:
- is the vulnerable code path actually used here?
- what should be upgraded?
- what compatibility work is needed?
A practical pattern
A common Jean workflow looks like this:
- Load the GitHub issue, PR, alert, or Linear ticket.
- Create the worktree directly from that item.
- Let Jean start the matching investigation flow.
- Keep a second session tab for implementation or review.
- Use magic commands for commit, PR content, or review comments.