Local Review

Set up a Git worktree for reviewing a colleague's GitHub branch.

4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/visualitypl/visuality-humanlayer --skill local-review-visualitypl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Local Review
Source: https://github.com/visualitypl/visuality-humanlayer/tree/main/.github/skills/local_review
Command: npx skills add https://github.com/visualitypl/visuality-humanlayer --skill local-review-visualitypl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of setting up a local development environment to review a colleague's code branch, ensuring a smooth and efficient code review workflow.

Core Features & Use Cases

  • Automated Worktree Setup: Creates a dedicated worktree for a specified GitHub branch.
  • Dependency Management: Configures necessary project settings and dependencies within the new worktree.
  • Use Case: When a colleague shares a branch like username:feature/new-login-flow, you can use this Skill to quickly set up a separate directory to clone, build, and test their changes without disrupting your own work.

Quick Start

Use the local review skill to set up a worktree for the branch username:branchname.

Frequently Asked Questions about Local Review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a git worktree to review a colleague's branch without disrupting my current work?

To set up a git worktree for code review, you need to add a remote for your colleague, fetch their branch, and create a separate worktree directory. This isolates their changes so you can build and test without affecting your current development environment.

Can I parse GitHub usernames and ticket information from a branch name when creating a worktree?

Yes, when creating a worktree, the system can parse GitHub usernames and branch names to automatically extract ticket information. This extracted ticket data is then used to generate a structured directory name for the new worktree.

What is the best way to handle worktree conflicts during a local code review setup?

The best way to handle worktree conflicts is to use an automated setup process that manages potential directory collisions. This ensures your local review environment is configured correctly without overwriting existing worktrees or causing Git conflicts.

Do I need to manually configure local settings and dependencies after creating a worktree for a GitHub branch?

No, you do not need to manually configure local settings. The worktree setup process handles fetching the colleague's branch and automatically configures the necessary local settings and dependencies within the new directory.