creating-pr

# Creating PR

## Overview

Create GitHub pull requests following a standardized format with proper Conventional Commits types and draft status.

## PR Creation Workflow

### 1. Analyze Current State

Check the current branch and merge target:

```bash
# Get current branch
git branch --show-current

# Check remote tracking and base branch
git status
```

### 2. Gather Change Information

Collect information about the changes:

```bash
# Get commit history from base branch
git log origin/main..HEAD --oneline

# Get detailed diff from base branch
git diff origin/main...HEAD --stat
git diff origin/main...HEAD
```

Replace `origin/main` with the actual base branch (e.g., `origin/master`, `origin/develop`).

### 3. Analyze Changes and Determine Type

Analyze the changes and determine the appropriate Conventional Commits type:

- Read [commit-types.md](references/commit-types.md) for detailed type selection guidelines
- Consider the primary purpose of the changes
- Follow the priority order: feat > fix > perf > refactor > test > docs > chore

### 4. Create PR Title

Format: `[base-branch] type: description`

**Components:**
- `[base-branch]`: The target branch name (e.g., `main`, `master`, `develop`)
- `type`: Conventional Commits type (feat, fix, chore, docs, refactor, test, perf, style, ci, build)
- `description`: Concise summary of changes in lowercase

**Examples:**
- `[main] feat: add user authentication system`
- `[main] fix: resolve null pointer in login handler`
- `[develop] refactor: extract validation logic`

### 5. Create PR Description

Generate a concise bullet-point list of main changes:

**Format:**
```markdown
- Main change 1
- Main change 2
- Main change 3
```

**Guidelines:**
- Focus on user-facing or significant technical changes
- Keep each point concise (one line)
- Limit to 3-5 main points
- Use imperative mood (e.g., "Add", "Fix", "Update")

**Example:**
```markdown
- Add JWT authentication middleware
- Implement user login and logout endpoints
- Ad