[RELEASE] v2.2.6 PR 생성 시 테스트 자동 실행 CI 워크플로우 추가

[pooreumjung]

#️⃣ Issue Number

• resolved feature: PR 생성 시 테스트 자동 실행하는 CI 워크플로우 추가 #385, fix: Ratings.of()에서 amountRating/tasteRating null 시 NullPointerException 발생 #387, fix: NicknameValidator 시작/끝 문자 검증 정규식에 숫자가 허용되어 있어 검증 누락 #388

📝 요약(Summary)

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces significant improvements to the development workflow and project standards. It establishes clear conventions for code documentation, persistence layers, and testing, while refining the interaction guidelines for AI-assisted development. Additionally, it enhances validation logic in the domain layer and updates test suites to better reflect current business rules, alongside automating PR/Issue creation workflows.

Highlights

• CI/CD Workflow Update: Added automation for CI workflows upon PR creation to ensure testing consistency.
• Documentation and Standards: Added new documentation files for commenting, persistence, and testing conventions, and updated the CLAUDE.md file to streamline the AI interaction process.
• Code Refactoring and Validation: Updated Ratings entity validation logic and improved NicknameValidator test cases to align with updated business requirements.
• CLI Tooling: Enhanced .claude command templates to include automated issue and PR creation scripts with predefined labels and reviewers.

New Features

🧠 You can now enable Memory (public preview) to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/ci.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

---

Code standards set in stone, Tests run where seeds are sown. With workflows now in place, We win the development race.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

이번 풀 요청은 Claude 명령어 및 규칙 설정을 구체화하고, Ratings 엔티티의 평점 검증 로직 수정 및 NicknameValidatorTest 테스트 코드를 영어 메서드명과 given 주석을 추가하는 규칙에 맞게 개선하였습니다. 리뷰어는 Ratings 엔티티 내에서 외부 보안 라이브러리인 io.jsonwebtoken.lang.Assert를 사용하는 대신 표준 Java 예외(IllegalArgumentException)를 던지도록 변경하여 외부 의존성을 제거할 것을 권장하고 있습니다.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

도메인 엔티티에서 JWT 라이브러리의 내부 유틸리티 클래스인 io.jsonwebtoken.lang.Assert를 사용하는 것은 도메인 레이어가 외부 보안 라이브러리에 강하게 결합되는 설계적 문제가 있습니다. 표준 Java 예외(IllegalArgumentException)를 직접 던지거나 java.util.Objects를 사용하여 검증하는 것이 좋습니다.

Suggested change

	Assert.notNull(mainRating, "mainRating must not be null");
	validateRange(mainRating, "mainRating");
	if (mainRating == null) {
	throw new IllegalArgumentException("mainRating must not be null");
	}
	validateRange(mainRating, "mainRating");

References

1. 도메인 엔티티는 외부 라이브러리(특히 JWT 관련 라이브러리)에 의존하지 않고 순수하게 유지되어야 합니다.

[gemini-code-assist]

동일하게 validateRange 메서드에서도 io.jsonwebtoken.lang.Assert 대신 표준 Java 예외를 던지도록 변경하여 외부 라이브러리 의존성을 제거하는 것이 좋습니다.

    private static void validateRange(Integer rating, String fieldName) {
        if (rating == null) {
            return;
        }
        if (rating < 1 || rating > 5) {
            throw new IllegalArgumentException(fieldName + " must be between 1 and 5");
        }
    }

References

1. 도메인 엔티티는 외부 라이브러리(특히 JWT 관련 라이브러리)에 의존하지 않고 순수하게 유지되어야 합니다.