Git Worktree Tools - A CLI for managing Git worktrees with automatic file syncing.
gw simplifies Git worktree management with features like:
- Create worktrees with automatic file copying (
.env, secrets, configs) - Quick navigation with
gw cdand smart partial matching - Proxy commands for
git worktreeoperations with enhanced output
npm install -g @gw-tools/gw-tool# Create a new worktree (auto-creates branch if needed, auto-copies files)
gw add feature-auth
# Navigate to worktree
gw cd feature-auth
# Sync files between worktrees
gw sync feature-auth .env secrets/
# List all worktrees
gw list
# Remove when done
gw remove feature-auth📖 Full documentation: packages/gw-tool/README.md
Enhance your AI agent with gw-tools knowledge using skills.sh:
npx skills add https://github.com/mthines/gw-tools --skill @gw-git-worktree-workflows @gw-config-management @gw-multi-worktree-dev # installs all skills# Master Git worktrees and gw workflows
npx skills add https://github.com/mthines/gw-tools --skill @gw-git-worktree-workflows
# Configure gw for your project type (Next.js, monorepos, etc.)
npx skills add https://github.com/mthines/gw-tools --skill @gw-config-management
# Advanced parallel development patterns
npx skills add https://github.com/mthines/gw-tools --skill @gw-multi-worktree-devOnce installed, your AI agent can:
- Create worktrees for bug fixes and features automatically
- Configure gw for your specific project type
- Navigate between worktrees and manage files
- Create PRs from isolated worktrees
📖 Skill documentation: skills/README.md
This monorepo also includes utility libraries:
@gw-tools/strings- String manipulation utilities@gw-tools/async- Async utility functions with retry logic@gw-tools/colors- Color conversion and manipulation utilities@gw-tools/utils- Shared utilities (internal)
This repository uses Nx for monorepo management.
# Clone the repository
git clone <your-fork-url>
cd typescript-template
# Install dependencies
pnpm install
# Build all packages
npx nx run-many -t build
# Run tests
npx nx run-many -t test
# Lint all projects
npx nx run-many -t lint
# Run everything in parallel
npx nx run-many -t lint test build --parallel=3
# Visualize the project graph
npx nx graphThis repository showcases several powerful Nx features:
Enforces architectural constraints using tags. Each package has specific dependencies it can use:
scope:shared(utils) - Can be used by all packagesscope:strings- Can only depend on shared utilitiesscope:async- Can only depend on shared utilitiesscope:colors- Can only depend on shared utilities
Try it out:
# See the current project graph and boundaries
npx nx graph
# View a specific project's details
npx nx show project strings --webLearn more about module boundaries →
Packages can define custom commands beyond standard build/test/lint:
# Run the custom build-base command for strings package
npx nx run strings:build-base
# See all available targets for a project
npx nx show project stringsLearn more about custom run commands →
The CI pipeline includes nx fix-ci which automatically identifies and suggests fixes for common issues. To test it, you can make a change to async-retry.spec.ts so that it fails, and create a PR.
# Run tests and see the failure
npx nx test async
# In CI, this command provides automated fixes
npx nx fix-ciLearn more about self-healing CI →
Manage releases and publishing with Nx Release:
# Dry run to see what would be published
npx nx release --dry-run
# Version and release packages
npx nx release
# Publish only specific packages
npx nx release publish --projects=strings,colors├── packages/
│ ├── strings/ [scope:strings] - String utilities (publishable)
│ ├── async/ [scope:async] - Async utilities (publishable)
│ ├── colors/ [scope:colors] - Color utilities (publishable)
│ └── utils/ [scope:shared] - Shared utilities (private)
├── nx.json - Nx configuration
├── tsconfig.json - TypeScript configuration
└── eslint.config.mjs - ESLint with module boundary rules
This repository uses tags to enforce module boundaries:
| Package | Tag | Can Import From |
|---|---|---|
@gw-tools/utils |
scope:shared |
Nothing (base library) |
@gw-tools/strings |
scope:strings |
scope:shared |
@gw-tools/async |
scope:async |
scope:shared |
@gw-tools/colors |
scope:colors |
scope:shared |
The ESLint configuration enforces these boundaries, preventing circular dependencies and maintaining clean architecture.
To see module boundary enforcement in action:
- Try importing
@gw-tools/colorsinto@gw-tools/strings - Run
npx nx lint strings - You'll see an error about violating module boundaries
# Project exploration
npx nx graph # Interactive dependency graph
npx nx list # List installed plugins
npx nx show project strings --web # View project details
# Development
npx nx build strings # Build a specific package
npx nx test async # Test a specific package
npx nx lint colors # Lint a specific package
# Running multiple tasks
npx nx run-many -t build # Build all projects
npx nx run-many -t test --parallel=3 # Test in parallel
npx nx run-many -t lint test build # Run multiple targets
# Affected commands (great for CI)
npx nx affected -t build # Build only affected projects
npx nx affected -t test # Test only affected projects
# Release management
npx nx release --dry-run # Preview release changes
npx nx release # Create a new releaseNx Cloud ensures a fast and scalable CI pipeline. It includes features such as:
- Remote caching
- Task distribution across multiple machines
- Automated e2e test splitting
- Task flakiness detection and rerunning
Join the Nx community: