Review & Pull Requests

Tarsk includes a built-in diff viewer and pull request creation flow, so you can review and ship the agent’s work without leaving the app.

Review Mode

Click the Review button in the top toolbar (or Git Ops → View Diff) to open the diff viewer. The button shows a badge with the number of changed files when there are uncommitted changes.

The Diff Viewer

The diff viewer uses Monaco (the editor powering VS Code) and shows a side-by-side diff for every modified file:

• Left side — original (before changes)
• Right side — modified (after the agent’s changes)

Additions are highlighted in green, deletions in red, and modified lines in both.

Navigating Files

A file list on the left side of the diff viewer shows all changed files with their change type:

• Modified — file was changed
• Added — new file created
• Deleted — file was removed

Click any filename to jump to that file’s diff. The viewer also shows untracked files (new files not yet staged).

What to Look For

Use the diff viewer to:

• Verify the agent made only the changes you intended
• Catch unintended deletions or modifications
• Review generated code before committing
• Identify which files need manual follow-up

---

Creating a Pull Request

After reviewing and committing changes, create a pull request to merge the thread’s branch into your main branch.

Prerequisites

• The gh CLI must be installed and authenticated. Install from cli.github.com and run gh auth login.
• The project’s remote must be a GitHub repository.
• The branch must be pushed to the remote (use Git Ops → Push first).

Steps

1. Click Git Ops → Push to ensure the branch is pushed.
2. Click the Git Ops dropdown — if the project commit method is set to pull-request, a Create PR option appears.
3. Click Create PR. Tarsk: a. Sends the commit history and diff to the AI model. b. Generates a PR title and PR description in Markdown.
4. Review and edit the title and description in the dialog.
5. Click Create Pull Request.

The PR is created on GitHub via gh pr create. A link to the PR is shown so you can open it in your browser.

AI-Generated PR Description

The generated PR description typically includes:

• A summary of what changed and why
• A list of key changes grouped by file or feature area
• Any notable implementation decisions or caveats

You can edit the generated content freely before creating the PR.

Push Before PR Dialog

If the branch hasn’t been pushed when you attempt to create a PR, Tarsk shows a Push Before PR dialog. Click Push and Continue to push and then proceed with PR creation, or Cancel to go back and push manually.

---

Pull Request vs Direct Commit

The project’s Commit Method controls the default Git Ops button behaviour:

Setting	Behaviour
pull-request	After committing, prompts to create a PR. Suitable for team projects.
direct	Commits and pushes to the branch; no PR step.

Change this in Project Settings.

---

GitHub Status

For threads connected to a GitHub repository, Tarsk can detect:

• Whether the remote is a GitHub repo
• The repository URL
• Whether a PR already exists for the current branch

This information drives the Git Ops button state and PR creation flow.