FEAT: Add CodeRabbit yaml file by singsangssong · Pull Request #110 · focus-to-level-up/api-server

singsangssong · 2026-01-12T06:49:07Z

No description provided.

coderabbitai · 2026-01-12T06:49:15Z

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

📥 Commits

Reviewing files that changed from the base of the PR and between 55145d7 and b6daced.

📒 Files selected for processing (1)

.coderabbit.yaml

Tip

CodeRabbit can generate a title for your PR based on the changes.

Add @coderabbitai placeholder anywhere in the title of your PR and CodeRabbit will replace it with a title based on the changes in the PR. You can change the placeholder by changing the reviews.auto_title_placeholder setting.

Note

`.coderabbit.yaml` has unrecognized properties

CodeRabbit is using all valid settings from your configuration. Unrecognized properties (listed below) have been ignored and may indicate typos or deprecated fields that can be removed.

⚠️ Parsing warnings (1)

Validation error: Unrecognized key(s) in object: 'version', 'pre_merge_checks', 'tools'

⚙️ Configuration instructions

Please see the configuration documentation for more information.
You can also validate your configuration using the online YAML validator.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

✨ Finishing touches

🧪 Generate unit tests (beta)

✅ Unit Test PR creation complete.

Create PR with unit tests
Commit unit tests in branch feat/code-rabbit
Post copyable unit tests in a comment

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

coderabbitai · 2026-01-12T06:51:02Z

Note

Unit test generation is an Early Access feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Generating unit tests... This may take up to 20 minutes.

coderabbitai

Actionable comments posted: 4

🤖 Fix all issues with AI agents

In @.coderabbit.yaml:
- Line 65: Fix the Korean typo in the .coderabbit.yaml content by replacing "이떄"
with the correct form "이때" in the sentence that references HttpResponseUtils
(the line mentioning "이떄, `HttpResponseUtils` 클래스를 활용하여 일관된 응답 구조를 유지하는지
확인해주세요.").
- Around line 108-109: Replace the incorrect kebab-case key `osv-scanner` with
the schema-expected camelCase `osvScanner` so the tool setting is recognized
(preserve the nested `enabled: true` value); update any occurrences of
`osv-scanner` in this file to `osvScanner` including the top-level mapping used
to configure the OSV Scanner.
- Around line 91-100: The pre_merge_checks block is at the root level but must
be nested under the reviews section; move the entire pre_merge_checks mapping so
it is a child of reviews (ensure proper indentation and YAML structure) and
remove any duplicate root-level pre_merge_checks entries so the config under
reviews.pre_merge_checks (including title, description, docstrings,
issue_assessment and threshold) is applied.
- Around line 104-131: The `tools` section is at root level but must be nested
under the `reviews` key per schema; move the entire `tools:` block so it is a
child of `reviews:` (adjust indentation accordingly), ensuring YAML remains
valid (preserve all tool entries like gitleaks, osv-scanner, pmd, hadolint,
checkov, markdownlint, actionlint, yamllint, github-checks) and update any
CI/validation configs if they reference the previous path.

🧹 Nitpick comments (2)

.coderabbit.yaml (2)
34-34: 테스트 코드 제외에 대한 고려 사항

**/test/** 경로를 리뷰에서 제외하면 테스트 코드의 품질 문제(잘못된 assertion, 불완전한 mock 설정 등)를 놓칠 수 있습니다. 1인 개발 환경에서 테스트 코드는 특히 중요한 안전망 역할을 하므로, 필요시 이 필터를 제거하는 것을 고려해 보세요.

72-74: 가독성 개선: 섹션 간 빈 줄 추가 권장

path_instructions의 마지막 항목과 chat: 섹션 사이에 빈 줄이 없어 시각적으로 구분이 어렵습니다. YAML 문법상 문제는 없지만, 가독성을 위해 섹션 간 빈 줄을 추가하는 것을 권장합니다.
♻️ 수정 제안
         2. **Sentry Context**: 예외 처리(`catch`) 블록이나 중요 비즈니스 로직(결제, 공부 종료 등)에서 `Sentry.setUser()` 또는 `Sentry.setContext()`를 통해 디버깅 정보를 남기고 있는지 확인해주세요. 단순히 `log.error()`만 찍는 경우 Sentry 활용을 제안해주세요.
+
 chat:
   auto_reply: true

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 55145d7 and b6daced.

📒 Files selected for processing (1)

.coderabbit.yaml

coderabbitai · 2026-01-12T06:54:02Z

.coderabbit.yaml

+
+        ### Response Type
+        - 반환 타입은 항상 `ResponseEntity<ApiResponse<T>>` 형태의 통일된 응답 포맷을 권장합니다.
+        - 이떄, `HttpResponseUtils` 클래스를 활용하여 일관된 응답 구조를 유지하는지 확인해주세요.


⚠️ Potential issue | 🟡 Minor

오타 수정 필요

"이떄"는 "이때"의 오타입니다.

✏️ 수정 제안

- - 이떄, `HttpResponseUtils` 클래스를 활용하여 일관된 응답 구조를 유지하는지 확인해주세요. + - 이때, `HttpResponseUtils` 클래스를 활용하여 일관된 응답 구조를 유지하는지 확인해주세요.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

- 이떄, `HttpResponseUtils` 클래스를 활용하여 일관된 응답 구조를 유지하는지 확인해주세요.

- 이때, `HttpResponseUtils` 클래스를 활용하여 일관된 응답 구조를 유지하는지 확인해주세요.

🤖 Prompt for AI Agents

In @.coderabbit.yaml at line 65, Fix the Korean typo in the .coderabbit.yaml content by replacing "이떄" with the correct form "이때" in the sentence that references HttpResponseUtils (the line mentioning "이떄, `HttpResponseUtils` 클래스를 활용하여 일관된 응답 구조를 유지하는지 확인해주세요.").

coderabbitai · 2026-01-12T06:54:02Z

.coderabbit.yaml

+pre_merge_checks:
+  title:
+    mode: "warning"
+  description:
+    mode: "warning"
+  docstrings:
+    mode: "warning"
+    threshold: 50 # 문서화 커버리지 50% 권장
+  issue_assessment:
+    mode: "warning" # 연결된 이슈 해결 여부 확인


⚠️ Potential issue | 🟠 Major

pre_merge_checks가 잘못된 위치에 있습니다

스키마에 따르면 pre_merge_checks는 reviews 섹션 아래에 중첩되어야 합니다. 현재 루트 레벨에 위치해 있어 설정이 적용되지 않을 수 있습니다.

🔧 수정 제안

reviews: profile: "chill" # ... 다른 reviews 설정들 ... + + # 병합 전 체크 (스스로를 위한 안전장치) + pre_merge_checks: + title: + mode: "warning" + description: + mode: "warning" + docstrings: + mode: "warning" + threshold: 50 + issue_assessment: + mode: "warning" -# 병합 전 체크 (스스로를 위한 안전장치) -pre_merge_checks: - title: - mode: "warning" - description: - mode: "warning" - docstrings: - mode: "warning" - threshold: 50 - issue_assessment: - mode: "warning"

🤖 Prompt for AI Agents

In @.coderabbit.yaml around lines 91 - 100, The pre_merge_checks block is at the root level but must be nested under the reviews section; move the entire pre_merge_checks mapping so it is a child of reviews (ensure proper indentation and YAML structure) and remove any duplicate root-level pre_merge_checks entries so the config under reviews.pre_merge_checks (including title, description, docstrings, issue_assessment and threshold) is applied.

coderabbitai · 2026-01-12T06:54:02Z

.coderabbit.yaml

+tools:
+  # 보안 필수 (혼자 개발할 때 키 유출 실수가 잦음)
+  gitleaks:
+    enabled: true
+  osv-scanner: # 의존성 취약점 스캔
+    enabled: true
+
+  # Java 정적 분석
+  pmd:
+    enabled: true
+
+  # 인프라 (Docker)
+  hadolint:
+    enabled: true # Dockerfile 린트
+  checkov:
+    enabled: true # IaC 보안 점검
+
+  # 기타 유용한 툴
+  markdownlint:
+    enabled: true
+  actionlint:
+    enabled: true # GitHub Actions 린트
+  yamllint:
+    enabled: true
+
+  # GitHub Checks 통합 (PR 하단에서 상태 확인 가능)
+  github-checks:
+    enabled: true


⚠️ Potential issue | 🟠 Major

tools 섹션이 잘못된 위치에 있습니다

스키마에 따르면 tools는 reviews 섹션 아래에 중첩되어야 합니다. 현재 루트 레벨에 위치해 있어 정적 분석 도구 설정이 적용되지 않습니다.

🔧 수정 제안 - tools를 reviews 아래로 이동

reviews: profile: "chill" # ... 다른 reviews 설정들 ... + + # 툴 설정 (정적 분석 및 보안) + tools: + gitleaks: + enabled: true + osvScanner: + enabled: true + pmd: + enabled: true + hadolint: + enabled: true + checkov: + enabled: true + markdownlint: + enabled: true + actionlint: + enabled: true + yamllint: + enabled: true + github-checks: + enabled: true -# 툴 설정 (정적 분석 및 보안) -tools: - gitleaks: - enabled: true - osv-scanner: - enabled: true - # ... 이하 생략

🤖 Prompt for AI Agents

In @.coderabbit.yaml around lines 104 - 131, The `tools` section is at root level but must be nested under the `reviews` key per schema; move the entire `tools:` block so it is a child of `reviews:` (adjust indentation accordingly), ensuring YAML remains valid (preserve all tool entries like gitleaks, osv-scanner, pmd, hadolint, checkov, markdownlint, actionlint, yamllint, github-checks) and update any CI/validation configs if they reference the previous path.

coderabbitai · 2026-01-12T06:54:02Z

.coderabbit.yaml

+  osv-scanner: # 의존성 취약점 스캔
+    enabled: true


⚠️ Potential issue | 🟠 Major

잘못된 속성 이름: osv-scanner

스키마에 따르면 OSV Scanner 도구의 속성 이름은 osv-scanner(kebab-case)가 아닌 osvScanner(camelCase)입니다. 현재 이름으로는 설정이 인식되지 않습니다.

🔧 수정 제안

- osv-scanner: # 의존성 취약점 스캔 - enabled: true + osvScanner: # 의존성 취약점 스캔 + enabled: true

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

osv-scanner: # 의존성 취약점 스캔

enabled: true

osvScanner: # 의존성 취약점 스캔

enabled: true

🤖 Prompt for AI Agents

In @.coderabbit.yaml around lines 108 - 109, Replace the incorrect kebab-case key `osv-scanner` with the schema-expected camelCase `osvScanner` so the tool setting is recognized (preserve the nested `enabled: true` value); update any occurrences of `osv-scanner` in this file to `osvScanner` including the top-level mapping used to configure the OSV Scanner.

coderabbitai · 2026-01-12T07:14:30Z

✅ UTG Post-Process Complete

No new issues were detected in the generated code and all check runs have completed. The unit test generation process has completed successfully.

coderabbitai · 2026-01-12T07:14:32Z

Creating a PR to put the unit tests in...

The changes have been created in this pull request: View PR

FEAT: Add CodeRabbit yaml file

b6daced

coderabbitai bot reviewed Jan 12, 2026

View reviewed changes

coderabbitai bot mentioned this pull request Jan 12, 2026

CodeRabbit Generated Unit Tests: Add JUnit 5 tests for .coderabbit.yaml configuration #111

Open

singsangssong force-pushed the main branch from 3fbd00e to 5bfcb2f Compare January 16, 2026 08:17

singsangssong force-pushed the main branch from 8996d86 to 30691b7 Compare January 28, 2026 06:37

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

FEAT: Add CodeRabbit yaml file#110

FEAT: Add CodeRabbit yaml file#110
singsangssong wants to merge 1 commit intomainfrom
feat/code-rabbit

singsangssong commented Jan 12, 2026

Uh oh!

coderabbitai bot commented Jan 12, 2026 •

edited

Loading

`.coderabbit.yaml` has unrecognized properties

Uh oh!

coderabbitai bot commented Jan 12, 2026

Uh oh!

coderabbitai bot left a comment

Uh oh!

coderabbitai bot Jan 12, 2026

Uh oh!

coderabbitai bot Jan 12, 2026

Uh oh!

coderabbitai bot Jan 12, 2026

Uh oh!

coderabbitai bot Jan 12, 2026

Uh oh!

coderabbitai bot commented Jan 12, 2026

Uh oh!

coderabbitai bot commented Jan 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

	- 이떄, `HttpResponseUtils` 클래스를 활용하여 일관된 응답 구조를 유지하는지 확인해주세요.
	- 이때, `HttpResponseUtils` 클래스를 활용하여 일관된 응답 구조를 유지하는지 확인해주세요.

Conversation

singsangssong commented Jan 12, 2026

Uh oh!

coderabbitai bot commented Jan 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

.coderabbit.yaml has unrecognized properties

Uh oh!

coderabbitai bot commented Jan 12, 2026

Uh oh!

coderabbitai bot left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot Jan 12, 2026

Choose a reason for hiding this comment

Uh oh!

coderabbitai bot commented Jan 12, 2026

Uh oh!

coderabbitai bot commented Jan 12, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

coderabbitai bot commented Jan 12, 2026 •

edited

Loading

`.coderabbit.yaml` has unrecognized properties