fix(skills): update link Code Review Comments

[r0mdau]

This pull request makes a minor update to the references in the .claude/skills/effective-go/SKILL.md documentation. The change updates the link for "Code Review Comments" to use the official Go website instead of the old GitHub wiki.

What this PR does / why we need it:

Broken link.

Checklist:

• Subject and description added to both, commit and PR.
• Relevant issues have been referenced.
• This change includes docs.
• This change includes unit tests.

[coderabbitai]

Walkthrough

Updated a URL reference in the Effective Go skill documentation, changing the Code Review Comments link from the GitHub wiki to the Go.dev wiki. No logic or content modifications.

Changes

Cohort / File(s)	Change Summary
Documentation reference update \.claude/skills/effective-go/SKILL.md	Updated Code Review Comments reference URL from GitHub wiki to Go.dev wiki

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to Reviews -> Disable Knowledge Base setting

📥 Commits

Reviewing files that changed from the base of the PR and between 7e919e2 and 9672b8a.

📒 Files selected for processing (1)

• .claude/skills/effective-go/SKILL.md (1 hunks)

🧰 Additional context used

🪛 markdownlint-cli2 (0.18.1)

.claude/skills/effective-go/SKILL.md

31-31: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (1)

.claude/skills/effective-go/SKILL.md (1)

31-31: ✓ URL update is correct and valid.

The Go wiki on GitHub has moved to go.dev, and https://go.dev/wiki/CodeReviewComments is the official canonical location. The link fix aligns with the documented migration.

One minor note: The static analysis flagged this line for a bare URL (MD034). While line 30 uses the same format, consider wrapping both reference URLs in markdown link syntax for consistency, e.g., [Code Review Comments](https://go.dev/wiki/CodeReviewComments). However, this may be a pre-existing pattern in the codebase—verify if markdown link formatting is required for references in this project.

---

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

[openshift-ci]

Hi @r0mdau. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: r0mdau
Once this PR has been reviewed and has the lgtm label, please assign muraee for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment