git-workspace-init
Initialize a new git worktree and branch for feature development or bug fixes. Use when: (1) Starting work on a new feature, (2) Beginning a bug fix, (3) Creating an isolated workspace for any task, (4) You want to work in parallel on multiple branches. This skill handles branch naming with conventi
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 428
- Лиценз
- Не е посочен. Проверете в репозитория.
- Последна проверка на записа
- Няма посочена дата
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add aiskillstore/marketplaceСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Git Workspace Init
Initialize an isolated git worktree with a properly named branch following conventional branch naming conventions.
When to Use
- Starting a new feature
- Beginning a bug fix
- Creating a hotfix
- Documentation updates
- Refactoring work
- Any task needing an isolated workspace
Prerequisites
- Git repository with a remote configured
- Write access to push branches
Workflow Overview
- Get task details → Ask for type and description (or accept from command)
- Generate branch name → Apply conventional branch naming
- Create worktree → Set up isolated workspace
- Push to remote → Track branch on origin
- Navigate → Switch to new workspace
Step 1: Gather Task Information
Ask the user for or accept from command arguments:
Task Type
| Type | Use Case | Example |
|---|---|---|
feat | New feature | feat/user-authentication |
fix | Bug fix | fix/login-validation-error |
hotfix | Urgent production fix | hotfix/security-patch |
docs | Documentation | docs/api-reference |
refactor | Code restructuring | refactor/extract-service |
test | Test additions | test/auth-integration |
chore | Maintenance | chore/upgrade-dependencies |
perf | Performance improvement | perf/optimize-queries |
ci | CI/CD changes | ci/add-deploy-workflow |
style | Code style/formatting | style/apply-prettier |
Task Description
A brief description that will become the branch name suffix:
- Use lowercase
- Use hyphens for spaces
- Keep it concise but descriptive
Examples:
- "user authentication" →
user-authentication - "fix validation error" →
validation-error - "add dark mode" →
dark-mode
Step 2: Generate Branch Name
Format: <type>/<description>
# Examples
feat/user-authentication
fix/null-pointer-exception
hotfix/xss-vulnerability
docs/installation-guide
refactor/extract-user-service
Naming Rules
- Lowercase only -
feat/Add-User→feat/add-user - Hyphens for spaces -
fix/login error→fix/login-error - No special characters - Only
a-z,0-9,-,/ - Concise - Keep under 50 characters total
- Descriptive - Should indicate the work being done