Prerequisites
- Git installed and configured
GitHub CLI (
gh) is optional. It’s only needed for:- Creating pull requests
- Viewing PR status badges on branches
- Browsing your GitHub repositories when cloning
Viewing Changes
Open the source control panel
Understanding file status
Files are marked with their status:| Icon | Status | Meaning |
|---|---|---|
| M | Modified | File has changes |
| A | Added | New file created |
| D | Deleted | File removed |
| R | Renamed | File moved or renamed |
| U | Untracked | New file not yet tracked |
View a file diff
Click any file in the source control panel to see its diff:- Red lines: Removed content
- Green lines: Added content
- Gray lines: Unchanged context
Reviewing Changes
What to look for
When reviewing AI-generated code, check for:Correctness
Correctness
- Does the code do what was asked?
- Are there logic errors?
- Are edge cases handled?
Security
Security
- Any hardcoded credentials?
- Input validation present?
- SQL injection possible?
- XSS vulnerabilities?
Quality
Quality
- Does it match your code style?
- Is it readable?
- Are names descriptive?
Completeness
Completeness
- Are tests included?
- Is error handling present?
- Documentation updated?
Adding inline comments
Click on a line
Click the line number where you want to comment. For multi-line comments, click a line number, hold, and drag to select multiple lines.
Staging Changes
Once you’re satisfied with the changes, stage them for commit.Stage all changes
Click Stage All to stage everything at once.Stage individual files
Unstage files
If you staged something by mistake:Discarding Changes
If you don’t want to keep the changes:Discard all changes
Discard specific files
Committing Changes
Pushing Changes
After committing, push to the remote:Creating a Pull Request
Creating PRs requires the GitHub CLI (
gh) to be installed and authenticated.Tips
Review frequently
Don’t let changes pile up. Review after each significant AI task:- AI completes a piece of work
- Review immediately
- Commit if good, or send back for fixes
- Continue
Use atomic commits
Make each commit a logical unit of work:- One feature per commit
- One bug fix per commit
- Don’t mix unrelated changes