docs(contributing): English-only language policy (#102)#106
Conversation
Repo language has been inconsistent: every shipped artifact (README, code, commits, CHANGELOG, all PR bodies) is in English, but 23 GitHub issues authored by an auditor agent (#58–#80) shipped in Korean. This commit adds a "Language" section to CONTRIBUTING.md so the standard is repo-discoverable and not just agent-memory-only. The auditor agent's persistent memory was already hard-locked to English on 2026-04-25; this is the project-side guardrail. Body-level translation of issues #58–#80 is tracked separately under #102 and applied via gh issue edit (no git history rewrite). Refs #102 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
개요프로젝트의 기본 언어를 영어로 설정하는 새로운 언어 정책 섹션이 CONTRIBUTING.md에 추가되었습니다. Claude Code 상호작용 시 한국어 프롬프트는 언어 전환 신호로 간주되지 않으며, 명시적 지시가 없는 한 영어로 응답해야 한다는 지침이 포함되었습니다. 변경 사항
예상 코드 리뷰 노력🎯 1 (간단함) | ⏱️ ~3분 시
🚥 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)
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 |
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@CONTRIBUTING.md`:
- Around line 9-15: The CONTRIBUTING.md currently enforces "English-only" but
contains the LESSON template labels "문제/원인/해결/참조", creating a contradiction;
update CONTRIBUTING.md to remove ambiguity by either (A) converting the LESSON
template labels to English (e.g., "Problem/Cause/Solution/References") wherever
the LESSON format appears, or (B) adding a short explicit exception clause under
the English-only policy that allows those specific template labels to remain in
Korean; make the change in the CONTRIBUTING.md LESSON template and any nearby
policy sentence so the document is consistent and unambiguous.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| All issues, PRs, commits, code, and documentation in this repo are written in | ||
| **English**. This keeps the artifact archive uniform and accessible to | ||
| non-Korean reviewers, and matches the standard already followed by every | ||
| shipped commit, PR body, CHANGELOG entry, and code comment. Korean prompts | ||
| during a Claude Code session are not a switch signal — agents should reply | ||
| in English by default. Make exceptions only for explicit, single-turn user | ||
| directives. |
There was a problem hiding this comment.
영어 전용 선언이 동일 문서 내 한국어 템플릿과 충돌합니다.
CONTRIBUTING.md에서 “모든 문서 영어”를 선언했지만, 같은 파일의 LESSON 포맷(문제/원인/해결/참조)은 한국어라 정책 해석이 모호해집니다. 정책 문구에 예외를 명시하거나 해당 템플릿 라벨을 영어로 맞춰 일관성을 확보해 주세요.
제안 수정안 (예: 템플릿 라벨 영어화)
### N.M One-line summary
-- **문제**: …
-- **원인**: …
-- **해결**: …
-- **참조**: …
+- **Problem**: …
+- **Cause**: …
+- **Resolution**: …
+- **Reference**: …🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@CONTRIBUTING.md` around lines 9 - 15, The CONTRIBUTING.md currently enforces
"English-only" but contains the LESSON template labels "문제/원인/해결/참조", creating a
contradiction; update CONTRIBUTING.md to remove ambiguity by either (A)
converting the LESSON template labels to English (e.g.,
"Problem/Cause/Solution/References") wherever the LESSON format appears, or (B)
adding a short explicit exception clause under the English-only policy that
allows those specific template labels to remain in Korean; make the change in
the CONTRIBUTING.md LESSON template and any nearby policy sentence so the
document is consistent and unambiguous.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 731b563f9c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| All issues, PRs, commits, code, and documentation in this repo are written in | ||
| **English**. This keeps the artifact archive uniform and accessible to |
There was a problem hiding this comment.
Reconcile English-only rule with LESSON submission format
The new statement that all repo artifacts are written in English conflicts with the currently required LESSON workflow, which is explicitly defined as 문제 → 원인 → 해결 → 참조 in both the LESSON issue template (.github/ISSUE_TEMPLATE/lesson_contribution.yml:11,40-58) and this same guide (CONTRIBUTING.md:114-117). Contributors following the new rule will reasonably translate these fields to English, creating inconsistent submissions and avoidable triage friction for the LESSON pipeline.
Useful? React with 👍 / 👎.
Summary
Adds a "Language" section to
CONTRIBUTING.mdso the English-only standard is repo-discoverable rather than living only in agent memory.Repo language has been inconsistent: shipped artifacts (README, code, commits, CHANGELOG, PR bodies) are English, but 23 issues from an auditor agent (#58–#80) shipped in Korean — see #102 for the root cause analysis.
Test plan
head -10 CONTRIBUTING.mdshows the new sectionCodex review
Skipped this pass — single-paragraph documentation addition, zero code surface, no behavior change.
Refs #102 (does not close — body-level translation of #58–#80 is the remaining acceptance-criteria item)
Summary by CodeRabbit
문서