Pynchy Worktrees

Overview

Pynchy Worktrees enable safe, isolated workspaces for teams with pynchy_repo_access. It helps you reason about git worktree isolation, diagnose leftover uncommitted changes after service restarts, and understand post-run merges across worktrees. This skill supports clean, traceable development in multi-user environments.

How This Skill Works

The skill leverages Git's worktree feature to create, monitor, and clean up separate working directories tied to a single repository. It emphasises access control for non-admin groups and provides checks for uncommitted work left behind after restarts, plus guidance on how post-run merges behave across worktrees during typical workflows.

When to Use It

• When collaborating with non-admin teams that have pynchy_repo_access and need isolated workspaces
• After a service restart to diagnose uncommitted changes left in a worktree
• To understand and validate post-run merge behavior across worktrees
• While debugging unexpected cross-worktree changes from git worktree usage
• During audits of worktree isolation and repository access policies

Quick Start

1. Step 1: Verify you have pynchy_repo_access for the target group.
2. Step 2: Create and switch to a new worktree (git worktree add -b feature-branch /path/to/worktree origin/feature-branch).
3. Step 3: After work is complete, merge if needed and prune unused worktrees (git commit/merge as appropriate, then git worktree prune).

Best Practices

• Require pynchy_repo_access before creating a worktree
• Regularly enumerate and prune unused worktrees to prevent leaks
• Check each worktree for uncommitted changes after restarts
• Document post-run merge expectations and outcomes for reproducibility
• Test changes in a sandbox worktree before merging to main branches

Example Use Cases

• Create a feature worktree for a non-admin group with repo access to isolate work and track changes
• Diagnose leftovers after a service restart by listing worktrees and inspecting status
• Validate that post-run merges are correctly reflected in the target branch
• Audit active worktrees to ensure isolation boundaries are respected
• Prune stale worktrees to reclaim disk space and maintain repo hygiene

Frequently Asked Questions