[REFAC#303] GoDoc 정합성 보강 — exported 식별자 docstring 첫 단어 식별자명 일치

[juhy0987]

연관 이슈

• Closes [REFACTOR] GoDoc 정합성 보강 — exported 식별자 docstring 첫 단어 식별자명 일치 + 부재 시 추가 #303

구현 내용

#301 (PR #302) 의 후속. godoc 컨벤션 위반 검출 + 정정.

검출 결과

awk 스크립트로 `internal/`, `pkg/`, `cmd/` 의 exported func/type/const/var 직전 godoc 검사:

항목	카운트
MISMATCH (첫 단어가 식별자명 아님)	1건
MISSING (godoc 부재)	16건
본 PR 처리 대상	5건
처리 제외 (`internal/classifier/grpc/pb/*.pb.go` generated code)	12건

정정 5건

1. `internal/storage/parsing_rule.go:23` MISMATCH `TargetTypeArticle`
   • 첫 단어 "호환성" → "TargetTypeArticle 은 ..." 으로 정정 (Deprecated 마커 보존)
2. `internal/processor/fetcher/domain/general/handler.go:51` MISSING `NewGoQueryFetchHandler`
3. `internal/processor/fetcher/domain/general/handler.go:113` MISSING `NewBrowserFetchHandler`
4. `internal/processor/fetcher/domain/general/fetcher/browser.go:26` MISSING `NewBrowserFetcher`
5. `internal/processor/fetcher/domain/general/fetcher/goquery.go:19` MISSING `NewGoqueryFetcher`

Generated code 12건 제외 사유

• `internal/classifier/grpc/pb/classifier.pb.go` / `classifier_grpc.pb.go` — protoc 가 자동 생성
• 직접 godoc 추가 시 다음 `protoc` 호출에 사라짐
• golangci-lint 도 보통 generated code 제외 (`//nolint` 또는 `exclude-files`)

CI / 머지 게이트 점검

변경 영향 범위

• 영향: 4개 `.go` 파일의 godoc only — 기능적 변경 0
• 위험도: `Low`

Required Status Checks

• 통과 확인 대상:
  • `Commit Lint`
  • `PR Title Lint`
  • `Linked Issue Check`
  • `Format Check`
  • `Build`
  • `Test`
  • `Lint`

로컬 검증 통과

• `go build` 통과
• `go test ./...` 통과 (35 패키지)
• `go vet` 통과
• `gofmt` 적용
• 검출 스크립트 재실행 → 0 violation (generated code 제외)

롤백 계획

PR revert — 기능 변경 0 이라 영향 없음.

TODO (후속 권장)

• `test/` 디렉토리 godoc 검토 — 본 PR scope 외
• `internal/classifier/grpc/pb/*.pb.go` 의 godoc 은 `.proto` 파일에 도입 (protoc-gen-go-doc 활용) 또는 protobuf 파일 자체에 docstring 작성

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@juhy0987 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 24 minutes and 36 seconds before requesting another review.

To continue reviewing without waiting, purchase usage credits in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a4bc849c-c555-4e8e-b4f4-b83aa236d6ce

📥 Commits

Reviewing files that changed from the base of the PR and between 7c8a9a5 and 6f3771a.

📒 Files selected for processing (4)

• internal/processor/fetcher/domain/general/fetcher/browser.go
• internal/processor/fetcher/domain/general/fetcher/goquery.go
• internal/processor/fetcher/domain/general/handler.go
• internal/storage/parsing_rule.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch refactor/#303/godoc-consistency

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request adds documentation comments to several fetcher and handler constructors and updates compatibility notes for TargetTypeArticle. The review feedback suggests standardizing the naming of GoQuery across the project for consistency and refining the documentation for fetch handlers to focus on their specific roles rather than their current position in the execution chain to ensure the comments remain accurate if the chain structure changes.