dev

Files (1)

• SKILL.md

SKILL.md (first lines)

# Dev Skill — Feature Branch Workflow Automation

Create a feature branch, do the work in a worktree, then automatically merge back to the current branch and clean up.

## Usage

```
/dev "brief feature description"
/dev --branch custom-name "feature description"
/dev --abort [branch-name]
```

## Argument Handling

Extract the following from `$ARGUMENTS`:

1. **Feature description** (required, except for `--abort`): a quoted string describing what to implement concisely
2. **--branch** (optional): specify the branch name directly. Skips prefix detection and uses the given name as-is (e.g. `--branch hotfix/urgent` → branch name `hotfix/urgent`)
3. **--abort** (optional): abort an in-progress dev workflow and clean up the worktree

### `--abort` Handling

```bash
# 1. If branch-name is provided: find the worktree for that branch
# 2. If branch-name is omitted: print the worktree list and guide the user to re-run with a branch name
git worktree list
```

Output when branch-name is not specified:
```
Current registered worktrees:
{git worktree list output}

Specify the branch to clean up and run again:
  /dev --abort feat/my-feature
```

When branch-name is specified:
```bash
# Check for unmerged commits
git log "$BASE_BRANCH".."$BRANCH_NAME" --oneline

# Warn if commits exist
```

Confirmation message when there are unmerged commits:
```
[WARNING] This branch has {N} unmerged commit(s):
{commit list}

These commits cannot be recovered after deletion. Do you want to proceed?
```
**→ Use `AskUserQuestion` to request confirmation and wait for the user's response. Do not proceed with deletion until a response is received.**

After user confirmation:
```bash
WORKTREE_DIR=$(echo "$BRANCH_NAME" | tr '/' '-')
WORKTREE_PATH="../${PROJECT_NAME}-${WORKTREE_DIR}"

git worktree remove --force "$WORKTREE_PATH"

# Attempt safe delete → force delete only after user confirmation above
git branch -d "$BRANCH_NAME" || git branch -D "$BRANCH_NAME"  # -D only after confirmation above
```

### Automatic Branch Name Generation

Detect the **type of change** from the feature description to determine the prefix:

| Detected keywords | prefix | Example |
|-------------------|--------|---------|
| "fix", "bug", "error" | `fix/` | `fix/pty-path-bug` |
| "refactor", "cleanup", "improve" | `refactor/` | `refactor/mcp-server` |
| "docs", "README", "comment" | `docs/` | `docs/update-readme` |
| anything else (default) | `feat/` | `feat/add-dashboard` |

Slug generation rules:
- Translate non-English words to English (e.g. "PTY bug fix" → `fix/pty-bug`)
- Replace spaces/special characters with hyphens
- Maximum 30 characters, lowercase

### Worktree Path Generation

Replace `/` in the branch name with `-` for the worktree path:
```bash
WORKTREE_DIR=$(echo "$BRANCH_NAME" | tr '/' '-')
WORKTREE_PATH="../${PROJECT_NAME}-${WORKTREE_DIR}"
# Example: feat/add-dashboard → ../oh-my-til-feat-add-dashboard
```

## Path Rules (Important)

Claude Code's Bash tool does not preserve shell state (including `cd`) between calls. Therefore:

- **Use absolute paths in all bash commands**
- When working in a worktree: prefix every command with the absolute path of `$WORKTREE_PATH`
- When editing files (Read/Edit tools): reference files by their absolute path under `$WORKTREE_PATH`
- After Phase 5: use the absolute path of `$PROJECT_ROOT`
- Use literal absolute path strings rather than variable references (e.g. `/Users/.../oh-my-til-feat-xxx/src/main.ts`)

## Pre-flight Validation

Check all conditions below. Abort and notify the user if any one fails.

1. **Verify the working tree is clean**
   ```bash
   git status --porcelain
   ```
   Abort if there are uncommitted changes.

2. **Check the current branch**
   ```bash
   git branch --show-current
   ```
   - Abort if the output is empty (detached HEAD): "Cannot run in detached HEAD state"
   - Abort if on `main`: "Do not work directly on main. Run from a release or other branch"
   - If on a `release/*` branch, print: "[INFO] Running from release branch ({name}). Merge target: {name}"
   - Save the current branch as `BASE_BRANCH` (merge target)

From SongYunSeop/oh-my-til, MIT.

More from SongYunSeop/oh-my-til