impl-wt-en

Implement code changes in isolated Git worktrees and create pull requests.

Updated Feb 9, 2026

Search Tags:#code review #development workflow #pull request #issue tracking #git worktree #code implementation

Ready to run

npx skills add https://github.com/ousiass/claude-config --skill impl-wt-en

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: impl-wt-en
Source: https://github.com/ousiass/claude-config/tree/main/skills/impl-wt-en
Command: npx skills add https://github.com/ousiass/claude-config --skill impl-wt-en

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill allows you to implement code changes within a dedicated Git worktree, ensuring your main working directory remains clean and unaffected until your changes are ready for review and merging.

Core Features & Use Cases

Isolated Development: Work on features or fixes in a separate Git worktree, preventing interference with your main codebase.
Phased Implementation: Follows a structured process of planning, development, review, and refinement for each code scope.
Automated PR Creation: Facilitates the creation of pull requests directly from the worktree.
Use Case: When working on a new feature, you can use this Skill to create a worktree, implement the feature in isolation, and then generate a pull request without cluttering your primary development branch.

Quick Start

Use the impl-wt-en skill to implement the requirements from issue number 123.

Frequently Asked Questions about impl-wt-en

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

FAQPage Schema

How do I implement code changes in an isolated Git worktree without affecting my main branch?▼

Implementing code changes in an isolated Git worktree involves creating a separate working directory for your feature, allowing phased development and automated pull request creation without cluttering your primary branch.

What is the best way to automate pull request creation from a Git worktree after finishing a feature?▼

Automating pull request creation from a Git worktree is handled by structuring the implementation cycle through planning, development, and review phases, then generating the pull request directly from the isolated worktree environment.

Can I integrate GitHub issue tracking with isolated Git worktree development workflows?▼

Yes, integrating GitHub issue tracking with isolated Git worktree development workflows is supported, allowing you to implement requirements directly from specific issue numbers while adhering to branch naming conventions.

Do I need to follow specific commit message standards when using Git worktrees for code implementation?▼

Yes, using Git worktrees for code implementation requires adhering to defined branch naming conventions and commit message standards to ensure your automated pull requests meet review requirements.

How does phased development work within a dedicated Git worktree for new features?▼

Phased development within a dedicated Git worktree follows a structured process of planning, development, review, and refinement for each code scope, ensuring iterative implementation before merging.

Why should I use an isolated Git worktree for code review and development workflows instead of branching?▼

Using an isolated Git worktree for code review and development workflows ensures your main working directory remains clean and unaffected, preventing interference until your changes are ready for review and merging.