Skip to content

Conversation

@2ghrms
Copy link
Member

@2ghrms 2ghrms commented Nov 21, 2025

#️⃣연관된 이슈

SRLT-63 AI 기능 파라미터 수정 및 프롬프트 보강

SRLT-80 Chore: 서브모듈 지칭 해시를 변경한다

SRLT-97 전문가 매칭에 따라서 사업계획서 상태를 업데이트한다

- 기존의 내용과 비교하는 방식에서 입력받은 것만 확인하도록 리팩토링
- 체크리스트용 프롬프트 @ConfigurationProperties로 매핑
- 일관성 유지 위한 ChatClient의 파라미터 수정
- 일관성 유지 위한 ChatClient의 파라미터 수정
- AiReportResponseParser에 대한 테스트 추가
…into SRLT-63-ai-기능-파라미터-수정-및-프롬프트-보강
[SRLT-63] AI 기능 파라미터 수정 및 프롬프트 보강
@2ghrms 2ghrms self-assigned this Nov 21, 2025
@2ghrms 2ghrms added the ☁️ DEPLOY 배포 관련 label Nov 21, 2025
@coderabbitai
Copy link

coderabbitai bot commented Nov 21, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

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: '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)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch develop

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@github-actions
Copy link

Test Results

250 tests   250 ✅  10s ⏱️
 48 suites    0 💤
 48 files      0 ❌

Results for commit b09218b.

@2ghrms 2ghrms merged commit 20bfc9d into main Nov 21, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

☁️ DEPLOY 배포 관련

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants