🧹 [コード健全性] fetchYearInReviewData 関数のリファクタリング

[is0692vs]

🎯 What: src/lib/githubYearInReview.ts の fetchYearInReviewData 関数が80行以上の複雑な構造だったため、可読性向上のためのリファクタリングを実施しました。
💡 Why: データ取得と変換ロジックが混在しており、メンテナンスしにくかったためです。クエリとデータ構築のロジックを分離することで、関数がシンプルになり保守性が向上します。
✅ Verification: lint、型チェック、単体テスト (npm run lint, npx tsc --noEmit, npm run test -- --run) を全て通過することを確認しました。
✨ Result: fetchYearInReviewData 関数の複雑度が減少し、責務が明確になりました。既存の機能に影響はありません。

---

PR created automatically by Jules for task 7899887911471908513 started by @is0692vs

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
github-user-summary	Ready	Preview, Comment	Mar 20, 2026 7:24am

[coderabbitai]

Warning

Rate limit exceeded

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

⌛ 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: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c691a0d1-ec39-4cf7-b209-6bcd9770005a

📥 Commits

Reviewing files that changed from the base of the PR and between 87d145d and 8c3d663.

📒 Files selected for processing (1)

• src/lib/githubYearInReview.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch refactor/github-year-in-review-query-7899887911471908513

📝 Coding Plan

• Generate coding plan for human review comments

---

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]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

src/lib/githubYearInReview.ts 内の fetchYearInReviewData 関数をリファクタリングし、可読性と保守性を向上させました。データ取得と変換ロジックを分離することで、関数がシンプルになり、責務が明確になりました。既存の機能への影響はありません。

Highlights

• リファクタリング: fetchYearInReviewData 関数をリファクタリングし、可読性と保守性を向上させました。
• ロジックの分離: データ取得とデータ構築のロジックを分離し、関数の責務を明確化しました。
• クエリの定義: GraphQLクエリを定数として定義し、コードの可読性を向上させました。
• データ構築関数の追加: buildYearInReviewData 関数を追加し、データ構築ロジックを独立させました。

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request refactors the fetchYearInReviewData function by extracting the GraphQL query into a dedicated constant (YEAR_IN_REVIEW_QUERY) and moving the data processing logic into a new buildYearInReviewData helper function to improve modularity. A review comment suggests an improvement to the newly introduced GraphQL query, recommending that the hardcoded maxRepositories: 10 value be converted into a variable for increased flexibility and maintainability.

[is0692vs]

レビュー内容を整理します。

全体所感

• gemini-code-assist: The pull request refactors the fetchYearInReviewData function by extracting the GraphQL query into a dedicated constant (YEAR IN REVIEW QUERY) and moving the data processing logic into a new buildYearInReviewData helper function to improve modularity. A review comment suggests...

主な未解決指摘

• [medium] src/lib/githubYearInReview.ts:45 gemini-code-assist: The hardcoded value maxRepositories: 10 appears in three places.

[google-labs-jules]

レビュー内容を整理します。

全体所感

• gemini-code-assist: The pull request refactors the fetchYearInReviewData function by extracting the GraphQL query into a dedicated constant (YEAR IN REVIEW QUERY) and moving the data processing logic into a new buildYearInReviewData helper function to improve modularity. A review comment suggests...

主な未解決指摘

• [medium] src/lib/githubYearInReview.ts:45 gemini-code-assist: The hardcoded value maxRepositories: 10 appears in three places.

ご指摘ありがとうございます。ハードコードされていた maxRepositories: 10 を GraphQL の変数 $maxRepositories に変更し、クエリ呼び出し時に引数として渡すように修正しました。すべてのテストが正常に通過することを確認済みです。