Skip to content

[#50] Discord report를 구조 단위 메시지로 분할한다 #64

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
opficdev merged 6 commits into from
Jul 18, 2026
Merged

[#50] Discord report를 구조 단위 메시지로 분할한다 #64

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
102c5d8
chore: 커밋 메시지 명사형 규칙 추가
opficdev Jul 18, 2026
44e5661
feat: Discord report 구조 단위 분할
opficdev Jul 18, 2026
a597906
feat: Discord AI report 단위 분할 구성
opficdev Jul 18, 2026
0ef1cde
feat: 긴 Suggested Patch 순번 분할과 code fence 재구성
opficdev Jul 18, 2026
f21c2c2
feat: Discord 전송 실패 위치 진단 추가
opficdev Jul 18, 2026
3cef37e
test: Discord report 분할 계약 검증 보강
opficdev Jul 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .agents/rules/project-workflows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,7 @@ This reference holds Watcher-specific working rules that should live with the pr

- Commit messages must start with a prefix such as `feat`, `fix`, `refactor`, or `chore`.
- Write commit message prose in Korean.
- 커밋 메시지의 한국어 설명은 서술형 종결어미를 사용하지 않고 `구성`, `추가`, `수정`, `정리` 같은 명사형으로 끝낸다.
- Keep implementation names, file paths, commands, branch names, workflow names, issue numbers, and commit hashes in their original form.
- Do not write a commit message body.
- Commit only files related to the current change.
Expand Down
Loading