release/1.1.0

.github/workflows/test.yaml

@@ -0,0 +1,20 @@
+name: CI - Build & Test (PushAndPull)
+on:
+  pull_request:
+    branches: ["*"]
+jobs:
+  build-and-test:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v4
+      - name: Setup .NET 9 SDK
+        uses: actions/setup-dotnet@v4
+        with:
+          dotnet-version: 9.0.x
+      - name: Restore dependencies
+        run: dotnet restore PushAndPull/PushAndPull.sln
+      - name: Build solution
+        run: dotnet build PushAndPull/PushAndPull.sln --configuration Release
+      - name: Run all tests
+        run: dotnet test PushAndPull/PushAndPull.sln --no-build --configuration Release --logger "trx;LogFileName=test_results.trx"

PushAndPull/.claude/commands/build.md

@@ -0,0 +1,16 @@
+---
+description: Build the server project and report errors
+allowed-tools: Bash
+---
+
+Build the server project and report any errors.
+
+## Steps
+
+1. Run the build command:
+   ```bash
+   dotnet build Server/Server.csproj
+   ```
+2. Check the build output:
+   - If the build **succeeds**: confirm success and show the summary (warnings, if any)
+   - If the build **fails**: list each error with its file path and line number, then explain the likely cause and how to fix it

PushAndPull/.claude/commands/commit.md

@@ -0,0 +1,49 @@
+---
+description: Create Git commits by splitting changes into logical units
+allowed-tools: Bash
+---
+
+Create Git commits following the project's commit conventions.
+
+## Commit Message Format
+
+```
+{type}: {Korean description}
+```
+
+**Types**:
+- `feat` — new feature added
+- `fix` — bug fix, missing config, or missing DI registration
+- `modify` — modification to existing code
+
+**Description rules**:
+- Written in **Korean**
+- Short and imperative (단문)
+- No trailing punctuation (`.`, `!` etc.)
+- Avoid noun-ending style — prefer verb style
+
+**Examples**:
+```
+feat: 방 생성 API 추가
+fix: 세션 DI 누락 수정
+modify: Room 엔터티 수정
+```
+
+**Do NOT**:
+- Add Claude as co-author
+- Write descriptions in English
+- Add a commit body — subject line only
+
+## Steps
+
+1. Check all changes with `git status` and `git diff`
+2. Categorize changes into logical units:
+   - New feature addition → `feat`
+   - Bug / missing registration fix → `fix`
+   - Modification to existing code → `modify`
+3. Group files by each logical unit
+4. For each group:
+   - Stage only the relevant files with `git add <files>`
+   - Write a concise commit message following the format above
+   - Execute `git commit -m "message"`
+5. Verify results with `git log --oneline -n {number of commits made}`

PushAndPull/.claude/commands/migrate.md

@@ -0,0 +1,24 @@
+---
+description: Add an EF Core migration and optionally update the database
+allowed-tools: Bash, Read
+---
+
+Add an EF Core migration using the name provided as the argument.
+
+Usage: `/migrate <MigrationName>`
+
+## Steps
+
+1. Run the migration command using the argument as the migration name:
+   ```bash
+   dotnet ef migrations add $ARGUMENTS --project Server
+   ```
+2. After the migration is created:
+   - Read the generated migration file under `Server/Migrations/`
+   - Briefly summarize what the migration does (tables created/altered, columns added/removed, indexes, etc.)
+3. Ask the user whether to apply the migration to the database:
+   - If yes, run:
+     ```bash
+     dotnet ef database update --project Server
+     ```
+   - Confirm the update result when done

PushAndPull/.claude/commands/pr.md

@@ -0,0 +1,191 @@
+---
+description: Generate PR title suggestions and body based on changes from develop
+allowed-tools: Bash(git log:*), Bash(git diff:*), Bash(git branch:*), Bash(git tag:*), Bash(git checkout:*), Bash(gh pr create:*), Bash(rm:*), Write, AskUserQuestion
+---
+
+Generate a PR based on the current branch. Behavior differs depending on the branch.
+
+## Context
+
+- Current branch: !`git branch --show-current`
+
+---
+
+## Branch-Based Behavior
+
+### Case 1: Current branch is `develop`
+
+**Step 1. Check the current version**
+
+- Check git tags: `git tag --sort=-v:refname | head -10`
+- Check existing release branches: `git branch -a | grep release`
+- Determine the latest version (e.g., `1.0.0`)
+
+**Step 2. Analyze changes and recommend version bump**
+
+- Commits: `git log main..HEAD --oneline`
+- Diff stats: `git diff main...HEAD --stat`
+- Recommend one of:
+  - **Major** (x.0.0): Breaking changes, incompatible API changes
+  - **Minor** (0.x.0): New backward-compatible features
+  - **Patch** (0.0.x): Bug fixes only
+- Briefly explain why you chose that level
+
+**Step 3. Ask user for version number**
+
+Use AskUserQuestion:
+> "현재 버전: {current_version}
+> 추천 버전 업: {Major/Minor/Patch} → {recommended_version}
+> 이유: {brief reason}
+>
+> 사용할 버전 번호를 입력해주세요. (예: 1.0.1)"
+
+**Step 4. Create release branch**
+
+```bash
+git checkout -b release/{version}
+```
+
+**Step 5. Write PR body** following the PR Body Template below
+- Analyze changes from `main` branch
+- Save to `PR_BODY.md`
+
+**Step 6. Create PR to `main`**
+
+```bash
+gh pr create --title "release/{version}" --body-file PR_BODY.md --base main
+```
+
+**Step 7. Delete PR_BODY.md**
+
+```bash
+rm PR_BODY.md
+```
+
+---
+
+### Case 2: Current branch is `release/x.x.x`
+
+**Step 1. Extract version** from branch name (e.g., `release/1.2.0` → `1.2.0`)
+
+**Step 2. Analyze changes from `main`**
+
+- Commits: `git log main..HEAD --oneline`
+- Diff stats: `git diff main...HEAD --stat`
+
+**Step 3. Write PR body** following the PR Body Template below
+- Save to `PR_BODY.md`
+
+**Step 4. Create PR to `main`**
+
+```bash
+gh pr create --title "release/{version}" --body-file PR_BODY.md --base main
+```
+
+**Step 5. Delete PR_BODY.md**
+
+```bash
+rm PR_BODY.md
+```
+
+---
+
+### Case 3: Any other branch
+
+**Step 1. Analyze changes from `develop`**
+
+- Commits: `git log develop..HEAD --oneline`
+- Diff stats: `git diff develop...HEAD --stat`
+- Detailed diff: `git diff develop...HEAD`
+
+**Step 2. Suggest 3 PR titles** following the PR Title Convention below
+
+**Step 3. Write PR body** following the PR Body Template below
+- Save to `PR_BODY.md`
+
+**Step 4. Output** in this format:
+```
+## 추천 PR 제목
+
+1. [title1]
+2. [title2]
+3. [title3]
+
+## PR 본문 (PR_BODY.md에 저장됨)
+
+[full body preview]
+```
+
+**Step 5. Ask the user** using AskUserQuestion:
+> "어떤 제목을 사용할까요? (1 / 2 / 3 또는 직접 입력)"
+
+**Step 6. Create PR to `develop`**
+
+- If the user answered 1, 2, or 3, use the corresponding suggested title
+- If the user typed a custom title, use it as-is
+
+```bash
+gh pr create --title "{chosen title}" --body-file PR_BODY.md --base develop
+```
+
+**Step 7. Delete PR_BODY.md**
+
+```bash
+rm PR_BODY.md
+```
+
+---
+
+## PR Title Convention
+
+Format: `{type}: {Korean description}`
+
+**Types:**
+- `feature` — new feature added
+- `fix` — bug fix or missing configuration/DI registration
+- `modify` — modification to existing code
+- `refactor` — refactoring without behavior change
+
+**Rules:**
+- Description in Korean
+- Short and imperative (단문)
+- No trailing punctuation
+
+**Examples:**
+- `feature: 방 생성 API 추가`
+- `fix: Key Vault 연동 방식을 AddAzureKeyVault으로 변경`
+- `refactor: 로그인 로직 리팩토링`
+
+---
+
+## PR Body Template
+
+Follow this exact structure (keep the emoji headers as-is):
+
+```
+## 📚작업 내용
+
+- {change item 1}
+- {change item 2}
+
+## ◀️참고 사항
+
+{additional notes, context, before/after comparisons if relevant. Write "." if nothing to add.}
+
+## ✅체크리스트
+
+> `[ ]`안에 x를 작성하면 체크박스를 체크할 수 있습니다.
+
+- [x] 현재 의도하고자 하는 기능이 정상적으로 작동하나요?
+- [x] 변경한 기능이 다른 기능을 깨뜨리지 않나요?
+
+
+> *추후 필요한 체크리스트는 업데이트 될 예정입니다.*
+```
+
+**Rules:**
+- Analyze commits and diffs to fill in `작업 내용` with a concise bullet list
+- Fill in `참고 사항` with any important context (architecture decisions, before/after, caveats). Write `.` if nothing relevant.
+- Keep total body under 2500 characters
+- Write in Korean
+- No emojis in text content (keep the section header emojis)

PushAndPull/.claude/commands/test.md

@@ -0,0 +1,16 @@
+---
+description: Run all tests and analyze failures
+allowed-tools: Bash
+---
+
+Run the full test suite and report results.
+
+## Steps
+
+1. Run all tests:
+   ```bash
+   dotnet test PushAndPull.sln --logger "console;verbosity=normal"
+   ```
+2. Check the test output:
+   - If all tests **pass**: confirm success and show the summary (total tests, duration)
+   - If any tests **fail**: list each failing test by name, show the failure message and stack trace, then explain the likely cause and how to fix it

PushAndPull/.claude/settings.json

@@ -0,0 +1,3 @@
+{
+  "hooks": {}
+}