Gemini でコードレビュー知見を見える化

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Slide 3

Slide 3 text

© ZOZO, Inc. ● ファッションEC ● 1,600以上のショップ、9,000以上のブランドの取り扱い ● 常時107万点以上の商品アイテム数と毎日平均2,700点以上の新着商品を掲載（2025年9月末時点） ● ブランド古着のファッションゾーン「ZOZOUSED」やコスメ専門モール「ZOZOCOSME」、シューズ専門ゾーン「ZOZOSHOES」、ラグジュアリー＆デザイナーズゾーン「ZOZOVILLA」を展開 ● 即日配送サービス ● ギフトラッピングサービス ● ツケ払いなど https://zozo.jp/ 3

Slide 4

Slide 4 text

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Slide 7

Slide 7 text

Slide 8

Slide 8 text

Slide 9

Slide 9 text

Slide 10

Slide 10 text

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

© ZOZO, Inc. Answer the following question in Japanese with Slack mrkdwn format, and output outline is like ':mag: Review trends', ':pencil: Development guideline updates', ':robot_face: Linter updates' : You're an fluent iOS senior engineer and good at following up your members skill. Read @pr-review-comments.md which summarizes the last 7 days pull request reviews and comments from your members. Based on the file, output review comment trends, perspectives that should be extracted as development guidelines, points that @.swiftlint.yml should be modified and suggest the basic rules or create SwiftLint custom rules and provide code if necessary. Assume SwiftLint version is ${{ env.SWIFTLINT_VERSION }}. レビュー観点の傾向を分析 Gemini にプロンプトを渡して Slack に結果を投稿する GitHub Actions を実行 16

Slide 17

Slide 17 text

© ZOZO, Inc. Answer the following question in Japanese with Slack mrkdwn format, and output outline is like ':mag: Review trends', ':pencil: Development guideline updates', ':robot_face: Linter updates' : You're an fluent iOS senior engineer and good at following up your members skill. Read @pr-review-comments.md which summarizes the last 7 days pull request reviews and comments from your members. Based on the file, output review comment trends, perspectives that should be extracted as development guidelines, points that @.swiftlint.yml should be modified and suggest the basic rules or create SwiftLint custom rules and provide code if necessary. Assume SwiftLint version is ${{ env.SWIFTLINT_VERSION }}. 英語で命令（日本語だと解釈がズレることがあった）日本語での返答を指定 Slack 書式で出力 17

Slide 18

Slide 18 text

© ZOZO, Inc. Answer the following question in Japanese with Slack mrkdwn format, and output outline is like ':mag: Review trends', ':pencil: Development guideline updates', ':robot_face: Linter updates' : You're an fluent iOS senior engineer and good at following up your members skill. Read @pr-review-comments.md which summarizes the last 7 days pull request reviews and comments from your members. Based on the file, output review comment trends, perspectives that should be extracted as development guidelines, points that @.swiftlint.yml should be modified and suggest the basic rules or create SwiftLint custom rules and provide code if necessary. Assume SwiftLint version is ${{ env.SWIFTLINT_VERSION }}. 投稿の書式を指定 🔎 レビュー傾向 ✏ 開発ルール更新案 🤖 Linter 更新案 18

Slide 19

Slide 19 text

© ZOZO, Inc. Answer the following question in Japanese with Slack mrkdwn format, and output outline is like ':mag: Review trends', ':pencil: Development guideline updates', ':robot_face: Linter updates' : You're an fluent iOS senior engineer and good at following up your members skill. Read @pr-review-comments.md which summarizes the last 7 days pull request reviews and comments from your members. Based on the file, output review comment trends, perspectives that should be extracted as development guidelines, points that @.swiftlint.yml should be modified and suggest the basic rules or create SwiftLint custom rules and provide code if necessary. Assume SwiftLint version is ${{ env.SWIFTLINT_VERSION }}. AI エージェントのペルソナを設定メンバースキルのフォローアップに卓越したシニア iOS エンジニアを想定 19

Slide 20

Slide 20 text

© ZOZO, Inc. Answer the following question in Japanese with Slack mrkdwn format, and output outline is like ':mag: Review trends', ':pencil: Development guideline updates', ':robot_face: Linter updates' : You're an fluent iOS senior engineer and good at following up your members skill. Read @pr-review-comments.md which summarizes the last 7 days pull request reviews and comments from your members. Based on the file, output review comment trends, perspectives that should be extracted as development guidelines, points that @.swiftlint.yml should be modified and suggest the basic rules or create SwiftLint custom rules and provide code if necessary. Assume SwiftLint version is ${{ env.SWIFTLINT_VERSION }}. 先ほど出力したレビューコメントファイルを読み込ませるファイル概要も説明する 20

Slide 21

Slide 21 text

© ZOZO, Inc. Answer the following question in Japanese with Slack mrkdwn format, and output outline is like ':mag: Review trends', ':pencil: Development guideline updates', ':robot_face: Linter updates' : You're an fluent iOS senior engineer and good at following up your members skill. Read @pr-review-comments.md which summarizes the last 7 days pull request reviews and comments from your members. Based on the file, output review comment trends, perspectives that should be extracted as development guidelines, points that @.swiftlint.yml should be modified and suggest the basic rules or create SwiftLint custom rules and provide code if necessary. Assume SwiftLint version is ${{ env.SWIFTLINT_VERSION }}. コメントファイルを元に投稿書式の内容を出力させる Linter 改善案は SwiftLint の標準ルール又はカスタムルールの提案 SwiftLint バージョンは環境変数で変更可能 21

Slide 22

Slide 22 text

Slide 23

Slide 23 text

Slide 24

Slide 24 text

© ZOZO, Inc. チーム共有・振り返り ● レビュアーが指摘の意図を語ってくれた ● 開発ルールの改定ポイント・理由をメンバー皆が観測できた ● 改定されたことで AI エージェントが賢くなった ● 把握してなかった SwiftLint の標準ルールが学べた ● .swiftlint.yml を初めて改修できたメンバーが現れたチームの週次定例で Slack 投稿をチェックしはじめて起こったこと 24

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

© ZOZO, Inc. チーム共有・振り返り ● レビュー傾向・開発ルール改善案が収束する ○ 同じことしか言わなくなる => AI 学習用ドキュメント更新フローが必要 ● カスタムルールの提案は全く採用されなかった ○ 恒常的に発生するミスにもとづく指摘ではなかった ○ カスタムルールを活かすためあえて SwiftFormat 非採用だった ○ => 現行・将来のカスタムルール必要性の議論後 Linter 変更検討もありチェックし続けてみた結果 27

Slide 28

Slide 28 text

© ZOZO, Inc. Q. Gemini を使ってるのは何故？ ● Claude Code/Codex が選択肢に入ったのはその後 ● とはいえ、コード生成ではない分析系だと Gemini でも問題ないと判断 ○ 変更するモチベーションが上がらず ○ Gemini 3.0 Pro が正式に利用できれば分析の質は向上するかも ● どのエージェントを使うかより、エージェントを賢くするループの設計が大事 A. 導入当時の選択肢が Gemini しかなかったからです 28