ci: PR 제목 Conventional 검증 추가 및 이슈/팀 설정 정비#95
Merged
Merged
Conversation
- pr-title.yml: 스쿼시 머지 시 PR 제목이 release-please 버전 산출에 쓰이므로 PR 제목이 Conventional Commits인지 CI에서 검사 (필수 체크로 등록 예정) - dotbugi에 맞게 정리한 .claude(팀 지침/rules/skills) 저장소 추적 - .gitignore: .hedwig-cg 인덱스, .claude/settings.local.json 제외 Closes #94
- task.yml: 기능/버그가 아닌 작업(문서·CI·리팩터 등)용 이슈 템플릿 - create-issue 스킬: gh issue create가 YAML 템플릿을 적용하지 않으므로, 스킬이 .github/ISSUE_TEMPLATE/*.yml을 읽어 그 구조대로 본문을 렌더링하도록 변경 (CLI 생성 이슈 = 웹 폼 이슈 동일 형태)
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
✅ Files skipped from review due to trivial changes (6)
📝 WalkthroughWalkthroughPR Changes팀 협업 지침 및 자동화 구성
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
.claude/skills/analyze-issue/SKILL.md (1)
13-15: ⚡ Quick win셸 예제 코드 블록에 언어를 지정해 주세요.
markdownlint가 이 파일들의 코드 블록을 경고로 잡고 있습니다.bash또는shell을 붙이면 lint 경고를 없애고 예제도 더 쉽게 복사할 수 있습니다.
analyze-issue:gh issue view/gh issue comment블록에 언어 태그 추가apply-pr-reviews:gh pr view/gh api블록에 언어 태그 추가create-issue:gh issue create블록에 언어 태그 추가create-pr:git/gh pr create블록에 언어 태그 추가🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.claude/skills/analyze-issue/SKILL.md around lines 13 - 15, Add a shell language tag to the fenced code blocks containing CLI examples so markdownlint stops warning; specifically, change the opening fences to "```bash" (or "```shell") for each affected site: in .claude/skills/analyze-issue/SKILL.md lines 13-15 (the "gh issue view <번호> ..." block) and lines 39-41 (the "gh issue comment" block), in .claude/skills/apply-pr-reviews/SKILL.md lines 13-15 and 21-25 (the "gh pr view" / "gh api" blocks), in .claude/skills/create-issue/SKILL.md lines 32-37 (the "gh issue create" block), and in .claude/skills/create-pr/SKILL.md lines 33-35 and 45-51 (the "git" / "gh pr create" blocks); no other code changes required.Source: Linters/SAST tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.claude/CLAUDE.md:
- Around line 23-27: Update the PR-title Conventional Commit types to match the
validator (include build, perf, style, revert alongside feat, fix, refactor,
chore, docs, test, ci) across the three files: in .claude/CLAUDE.md (lines
23-27) replace the current narrower list and examples so the allowed types
exactly mirror the validator and make the example PR title follow Conventional
Commits (use English if you decide to require English-only); in
.claude/rules/common.md (lines 13-14) update the allowed types list to the same
full set as the validator; and in .claude/skills/create-pr/SKILL.md (lines
19-27) change the allowed types to the validator’s full set and make the example
consistent with the chosen language policy (if requiring English, convert the
example to an English Conventional Commit title).
In @.claude/skills/apply-pr-reviews/SKILL.md:
- Around line 44-47: Update the CI verification step in "5단계: 검증·커밋" to include
Prettier format check so it matches the actual pr-checks; specifically add the
Prettier command (npx prettier --check .) to the list alongside `npm run lint` /
`npm run build` / `npm run test` so contributors run the same formatting check
locally before committing.
In @.claude/skills/hedwig-cg/SKILL.md:
- Around line 26-30: The markdown fenced code blocks at the listed sites lack
language tags and trigger MD040; add explicit language tags: for
.claude/skills/hedwig-cg/SKILL.md lines 26-30 and 44-53 mark those
example/description blocks as ```text (or convert them to normal markdown
paragraphs/lists), for .claude/skills/implement/SKILL.md lines 11-13, 21-24 and
38-42 mark the command examples as ```bash, for .claude/skills/issues/SKILL.md
lines 9-12 mark the command example as ```bash, for
.claude/skills/quality-review/SKILL.md lines 11-14 and 28-31 mark the command
examples as ```bash, for .claude/skills/refactor/SKILL.md lines 10-13 and 28-31
mark the command examples as ```bash, and for .claude/skills/repro-test/SKILL.md
lines 29-31 mark the command example as ```bash; no other code changes required.
In @.claude/skills/issues/SKILL.md:
- Line 14: The wording incorrectly calls the gh project item-list <번호> an "이슈
번호"; update the sentence to say that the parameter is a 프로젝트 번호 (or project URL)
not an issue number, e.g. clarify "gh project item-list <번호|프로젝트 URL> — 여기서
<번호>는 프로젝트 번호입니다" and adjust the example to show "프로젝트 '1'의 항목 나열" and note that
if the board is missing or read:project scope is absent it will skip and print
only issues; change the fragment referencing "이슈 번호" to "프로젝트 번호/URL" and keep
the rest of the behavior description unchanged.
---
Nitpick comments:
In @.claude/skills/analyze-issue/SKILL.md:
- Around line 13-15: Add a shell language tag to the fenced code blocks
containing CLI examples so markdownlint stops warning; specifically, change the
opening fences to "```bash" (or "```shell") for each affected site: in
.claude/skills/analyze-issue/SKILL.md lines 13-15 (the "gh issue view <번호> ..."
block) and lines 39-41 (the "gh issue comment" block), in
.claude/skills/apply-pr-reviews/SKILL.md lines 13-15 and 21-25 (the "gh pr view"
/ "gh api" blocks), in .claude/skills/create-issue/SKILL.md lines 32-37 (the "gh
issue create" block), and in .claude/skills/create-pr/SKILL.md lines 33-35 and
45-51 (the "git" / "gh pr create" blocks); no other code changes required.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 63e2bcf6-32b1-4341-93a5-6e60edd74662
📒 Files selected for processing (18)
.claude/CLAUDE.md.claude/rules/common.md.claude/rules/typescript.md.claude/settings.json.claude/skills/analyze-issue/SKILL.md.claude/skills/apply-pr-reviews/SKILL.md.claude/skills/compound/SKILL.md.claude/skills/create-issue/SKILL.md.claude/skills/create-pr/SKILL.md.claude/skills/hedwig-cg/SKILL.md.claude/skills/implement/SKILL.md.claude/skills/issues/SKILL.md.claude/skills/quality-review/SKILL.md.claude/skills/refactor/SKILL.md.claude/skills/repro-test/SKILL.md.github/ISSUE_TEMPLATE/task.yml.github/workflows/pr-title.yml.gitignore
- PR 제목 허용 타입을 pr-title.yml 기준으로 문서 통일(CLAUDE.md/common.md/create-pr) - apply-pr-reviews 검증 목록에 prettier --check 추가 - hedwig-cg 코드펜스에 text 언어 태그(MD040) - issues: gh project item-list <번호>는 프로젝트 번호임을 명확화
Member
Author
|
@coderabbitai review |
✅ Action performedReview finished.
|
3 tasks
This was referenced Jun 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #94
변경 내용
pr-title.yml: 스쿼시 머지 시 PR 제목이 release-please 버전 산출에 쓰이므로, PR 제목이 Conventional Commits인지 CI에서 검사 (머지 후 필수 체크로 등록 예정).github/ISSUE_TEMPLATE/task.yml: 버그/기능이 아닌 작업(문서·CI·리팩터 등)용 이슈 템플릿 추가/create-issue스킬:gh issue create가 YAML 템플릿을 적용하지 않으므로, 스킬이 템플릿 파일을 읽어 동일 구조로 본문을 렌더링하도록 변경.claude/: dotbugi에 맞게 정리한 팀 지침·rules·skills 저장소 추적 (개인 설정/로컬 인덱스는.gitignore)변경 유형
체크리스트
머지 후 (메인테이너)
PR 제목 검증체크를 main 브랜치 보호 필수 체크에 추가Summary by CodeRabbit
Documentation
Chores