Closed
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Contributor
개요두 개의 새로운 설계 및 구현 계획 문서가 docs/plans 디렉토리에 추가됩니다. feature-pr과 release-pr이라는 두 Claude 기술에 대한 설계 사양 및 구현 지침을 포함합니다. 변경사항
예상 코드 리뷰 노력🎯 2 (Simple) | ⏱️ ~12분 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
🤖 Fix all issues with AI agents
In `@docs/plans/2026-02-15-pr-skills-design.md`:
- Around line 36-69: The fenced code block in the PR template is missing a
language identifier which triggers lint warnings; update the opening ``` to
include a language (e.g., ```markdown or ```md) for the block in
docs/plans/2026-02-15-pr-skills-design.md so the linter recognizes the language
and the warning is resolved—locate the triple-backtick block that wraps the
template and change the delimiter to include the language identifier.
- Around line 13-18: 문서의 헤딩 레벨이 건너뛰어 한 단계씩 증가하지 않으므로 "Skill 1: `feature-pr`"와 하위
제목 "Start Phase (`/feature-pr start`)" 등 모든 헤더를 한 단계씩만 증가하도록 재조정하세요; 예를 들어 최상위
개요 다음은 H2, 그 하위는 H3로 맞추고 현재 H1→H3 같은 점프가 있는 곳을 찾아 각 헤더 토큰을 하나 레벨 낮추거나 올려 계층을
연속적으로 수정해 구조를 일관되게 만드세요.
- Around line 128-134: The fenced code block showing the directory tree
(~/.claude/skills/ with feature-pr/ and release-pr/ containing SKILL.md) lacks a
language identifier and triggers a lint warning; update that code block by
adding an appropriate language tag (e.g., ```bash or ```text) immediately after
the opening backticks so the linter recognizes the block type and the warning is
resolved.
In `@docs/plans/2026-02-15-pr-skills-impl-plan.md`:
- Around line 13-17: 문서의 헤딩 레벨이 건너뛰어져 있으므로 "Task 1: Create skills directory
structure" 같은 상위 헤딩부터 각 하위 섹션이 한 단계씩만 내려가도록 조정하세요; 즉 현재 한 단계 이상 건너뛴 헤딩들을 찾아서 모두
하나씩 올리거나(예: ### -> ####) 내려서(예: ## -> ###) 연속적인 레벨 흐름을 만들고, 목록에 있는 SKILL.md
플레이스홀더 항목들도 그에 맞춰 헤딩 레벨을 맞춰 정렬하세요.
- Around line 61-94: The fenced code block starting with ``` before the "##
Issue Number" section has no language identifier causing lint warnings; fix it
by changing the opening fence to include a language (e.g., add "markdown" or
"md" after the opening ```), and apply the same change to any other anonymous
fenced blocks in the document to remove the lint warning (locate the block by
the opening ``` and the "## Issue Number" header).
- Around line 138-149: The fenced code block that begins with ``` before the "##
Summary" section lacks a language identifier, causing lint warnings; change the
opening fence from ``` to ```markdown (or ```md) to mark the block as Markdown
so the linter recognizes it, and similarly add language identifiers to any other
untyped fenced blocks in the same file (look for the triple-backtick fences
surrounding "## Summary", "### Major Changes", etc.).
Comment on lines
+13
to
+18
|
|
||
| ## Skill 1: `feature-pr` | ||
|
|
||
| Lifecycle skill with two phases, invoked via args. | ||
|
|
||
| ### Start Phase (`/feature-pr start`) |
Contributor
There was a problem hiding this comment.
헤딩 레벨 점프를 정리하세요.
헤딩 레벨이 한 단계씩만 증가하도록 구조를 맞춰 주세요.
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)
[warning] 13-13: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
In `@docs/plans/2026-02-15-pr-skills-design.md` around lines 13 - 18, 문서의 헤딩 레벨이
건너뛰어 한 단계씩 증가하지 않으므로 "Skill 1: `feature-pr`"와 하위 제목 "Start Phase (`/feature-pr
start`)" 등 모든 헤더를 한 단계씩만 증가하도록 재조정하세요; 예를 들어 최상위 개요 다음은 H2, 그 하위는 H3로 맞추고 현재
H1→H3 같은 점프가 있는 곳을 찾아 각 헤더 토큰을 하나 레벨 낮추거나 올려 계층을 연속적으로 수정해 구조를 일관되게 만드세요.
Comment on lines
+36
to
+69
| ``` | ||
| ## Issue Number | ||
| DH-{id} | ||
|
|
||
| ## As-Is | ||
| ### 1. 기존 동작 및 문제 상황 | ||
| - {기존에 어떤 동작/상태였는지} | ||
| - {어떤 문제가 발생했는지} | ||
|
|
||
| ### 2. 대안 분석 (각 접근 방식의 장단점) | ||
| - {방식 A}: {장점} / {단점} | ||
| - {방식 B}: {장점} / {단점} | ||
|
|
||
| ## To-Be | ||
| ### 1. 최종 구현 결과 | ||
| - {구현된 핵심 내용} | ||
|
|
||
| ### 2. 기존 대비 변경 내역 | ||
| - {변경 전} → {변경 후} | ||
|
|
||
| ### 3. 미해결 이슈 및 향후 검토 사항 | ||
| - {남은 이슈 또는 추가 검토 필요 사항} | ||
|
|
||
| ## Check List | ||
| - [x] Have all tests passed? | ||
| - [x] Have all commits been pushed? | ||
| - [x] Did you verify the target branch for the merge? | ||
| - [ ] Did you assign the appropriate assignee(s)? | ||
| - [ ] Did you set the correct label(s)? | ||
|
|
||
| ## Test Screenshot | ||
|
|
||
| ## Additional Description | ||
| ``` |
Contributor
There was a problem hiding this comment.
코드 블록에 언어 식별자를 추가하세요.
fenced code block에 언어가 지정되지 않아 lint 경고가 발생합니다.
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)
[warning] 61-61: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In `@docs/plans/2026-02-15-pr-skills-design.md` around lines 36 - 69, The fenced
code block in the PR template is missing a language identifier which triggers
lint warnings; update the opening ``` to include a language (e.g., ```markdown
or ```md) for the block in docs/plans/2026-02-15-pr-skills-design.md so the
linter recognizes the language and the warning is resolved—locate the
triple-backtick block that wraps the template and change the delimiter to
include the language identifier.
Comment on lines
+128
to
+134
| ``` | ||
| ~/.claude/skills/ | ||
| feature-pr/ | ||
| SKILL.md | ||
| release-pr/ | ||
| SKILL.md | ||
| ``` |
Contributor
There was a problem hiding this comment.
코드 블록에 언어 식별자를 추가하세요.
fenced code block에 언어가 지정되지 않아 lint 경고가 발생합니다.
🤖 Prompt for AI Agents
In `@docs/plans/2026-02-15-pr-skills-design.md` around lines 128 - 134, The fenced
code block showing the directory tree (~/.claude/skills/ with feature-pr/ and
release-pr/ containing SKILL.md) lacks a language identifier and triggers a lint
warning; update that code block by adding an appropriate language tag (e.g.,
```bash or ```text) immediately after the opening backticks so the linter
recognizes the block type and the warning is resolved.
Comment on lines
+13
to
+17
| ### Task 1: Create skills directory structure | ||
|
|
||
| **Files:** | ||
| - Create: `~/.claude/skills/feature-pr/SKILL.md` (placeholder) | ||
| - Create: `~/.claude/skills/release-pr/SKILL.md` (placeholder) |
Contributor
There was a problem hiding this comment.
헤딩 레벨 점프를 정리하세요.
헤딩 레벨이 한 단계씩만 증가하도록 구조를 맞춰 주세요.
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)
[warning] 13-13: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents
In `@docs/plans/2026-02-15-pr-skills-impl-plan.md` around lines 13 - 17, 문서의 헤딩
레벨이 건너뛰어져 있으므로 "Task 1: Create skills directory structure" 같은 상위 헤딩부터 각 하위 섹션이 한
단계씩만 내려가도록 조정하세요; 즉 현재 한 단계 이상 건너뛴 헤딩들을 찾아서 모두 하나씩 올리거나(예: ### -> ####) 내려서(예:
## -> ###) 연속적인 레벨 흐름을 만들고, 목록에 있는 SKILL.md 플레이스홀더 항목들도 그에 맞춰 헤딩 레벨을 맞춰 정렬하세요.
Comment on lines
+61
to
+94
| ``` | ||
| ## Issue Number | ||
| DH-{id} | ||
|
|
||
| ## As-Is | ||
| ### 1. 기존 동작 및 문제 상황 | ||
| - {기존에 어떤 동작/상태였는지} | ||
| - {어떤 문제가 발생했는지} | ||
|
|
||
| ### 2. 대안 분석 (각 접근 방식의 장단점) | ||
| - {방식 A}: {장점} / {단점} | ||
| - {방식 B}: {장점} / {단점} | ||
|
|
||
| ## To-Be | ||
| ### 1. 최종 구현 결과 | ||
| - {구현된 핵심 내용} | ||
|
|
||
| ### 2. 기존 대비 변경 내역 | ||
| - {변경 전} → {변경 후} | ||
|
|
||
| ### 3. 미해결 이슈 및 향후 검토 사항 | ||
| - {남은 이슈 또는 추가 검토 필요 사항} | ||
|
|
||
| ## ✅ Check List | ||
| - [x] Have all tests passed? | ||
| - [x] Have all commits been pushed? | ||
| - [x] Did you verify the target branch for the merge? | ||
| - [ ] Did you assign the appropriate assignee(s)? | ||
| - [ ] Did you set the correct label(s)? | ||
|
|
||
| ## 📸 Test Screenshot | ||
|
|
||
| ## Additional Description | ||
| ``` |
Contributor
There was a problem hiding this comment.
코드 블록에 언어 식별자를 추가하세요.
fenced code block에 언어가 지정되지 않아 lint 경고가 발생합니다.
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)
[warning] 61-61: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In `@docs/plans/2026-02-15-pr-skills-impl-plan.md` around lines 61 - 94, The
fenced code block starting with ``` before the "## Issue Number" section has no
language identifier causing lint warnings; fix it by changing the opening fence
to include a language (e.g., add "markdown" or "md" after the opening ```), and
apply the same change to any other anonymous fenced blocks in the document to
remove the lint warning (locate the block by the opening ``` and the "## Issue
Number" header).
Comment on lines
+138
to
+149
| ``` | ||
| ## Summary | ||
|
|
||
| ### Major Changes | ||
| - {description} @{author-github-id} | ||
|
|
||
| ### Minor Changes | ||
| - {description} @{author-github-id} | ||
|
|
||
| ### Patch Changes | ||
| - {description} @{author-github-id} | ||
| ``` |
Contributor
There was a problem hiding this comment.
코드 블록에 언어 식별자를 추가하세요.
fenced code block에 언어가 지정되지 않아 lint 경고가 발생합니다.
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)
[warning] 138-138: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In `@docs/plans/2026-02-15-pr-skills-impl-plan.md` around lines 138 - 149, The
fenced code block that begins with ``` before the "## Summary" section lacks a
language identifier, causing lint warnings; change the opening fence from ``` to
```markdown (or ```md) to mark the block as Markdown so the linter recognizes
it, and similarly add language identifiers to any other untyped fenced blocks in
the same file (look for the triple-backtick fences surrounding "## Summary",
"### Major Changes", etc.).
Member
Author
|
브랜치 이름 변경으로 PR 재생성합니다 (codrin2/create-pr-skills → feat/DH-6) |
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.
Issue Number
DH-6
As-Is
1. 기존 동작 및 문제 상황
2. 대안 분석 (각 접근 방식의 장단점)
To-Be
1. 최종 구현 결과
feature-pr스킬: start/finish 2단계 라이프사이클 (브랜치 생성 → PR 작성)release-pr스킬: develop → main 릴리즈 PR (변경사항 분류 + 버전 제안 + 2단계 확인 게이트)2. 기존 대비 변경 내역
docs/plans/2026-02-15-pr-skills-design.md추가docs/plans/2026-02-15-pr-skills-impl-plan.md추가~/.claude/skills/feature-pr/SKILL.md스킬 파일 생성~/.claude/skills/release-pr/SKILL.md스킬 파일 생성3. 미해결 이슈 및 향후 검토 사항
~/.claude/skills/에 위치하여 repo에 포함되지 않음 (개인 설정)🚀 FEAT,🚨 FIX,🔋 REFACTOR) 사전 생성 필요 여부 확인✅ Check List
📸 Test Screenshot
Additional Description
스킬 파일(
~/.claude/skills/)은 개인 로컬 환경에 생성되며, 이 PR에는 설계/계획 문서만 포함됩니다.Summary by CodeRabbit
릴리스 노트