clone-worktree-port-bump

Clone a repository into ~/temp and bump *_PORT values in .env by 100 * N.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/tankygranny05/agent-box --skill clone-worktree-port-bump
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clone-worktree-port-bump
Source: https://github.com/tankygranny05/agent-box/tree/main/agent-box/seed/codex-skills/clone-worktree-port-bump
Command: npx skills add https://github.com/tankygranny05/agent-box --skill clone-worktree-port-bump

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents port collisions and accidental modifications to original codebases by creating isolated, port-adjusted clones of a project for concurrent development or testing.

Core Features & Use Cases

  • Safe Cloning: Creates a clean, independent copy of a repository in ~/temp.
  • Port Management: Automatically increments port numbers in .env files based on the clone number to avoid conflicts.
  • Isolation Enforcement: Ensures work is confined to the clone, protecting the original project.
  • Use Case: When multiple developers need to work on the same project simultaneously, or when running multiple instances of a service for testing, this skill ensures each has its own environment without port clashes.

Quick Start

Clone the current project to ~/temp, bump ports, and prepare it for isolated work.

Frequently Asked Questions about clone-worktree-port-bump

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

FAQPage Schema
How do I prevent port conflicts when running multiple clones of the same repository?

To prevent port conflicts with multiple clones, you can create an isolated worktree clone that automatically bumps *_PORT values in the .env file by an offset of 100 multiplied by the clone number, ensuring each instance uses unique ports.

How do I create an isolated git worktree clone for testing?

You can create an isolated git worktree clone by copying the repository into the ~/temp directory, which enforces working directory isolation to protect your original codebase from accidental modifications during concurrent testing.

Can I run multiple development environments from the same project without affecting the original codebase?

Yes, you can run multiple isolated development environments simultaneously by creating independent worktree clones in ~/temp, ensuring all subsequent operations and dependency installations are confined to the clone and do not modify the original repository.

What happens to the port numbers in my .env file when I create a worktree clone?

When you create a worktree clone, the port numbers in your .env file are automatically incremented by an offset of 100 * N, where N is the clone number, preventing network collisions across multiple active instances.

Why should I use a worktree clone instead of manually copying a repository for concurrent development?

Using a worktree clone is safer than manual copies because it automatically manages dependency installation, enforces working directory isolation, and systematically bumps port values in .env files to prevent conflicts without manual intervention.