Repository navigation
プロバイダーガイドの Next.js 移植（TDD）・a11y 改善および DeepSeek / OpenAI Codex 等の仕様・コード最適化 - #133
Merged
Merged
Conversation
✅ Deploy Preview for comparison-of-llms ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (11)
📝 WalkthroughSummary by CodeRabbit
WalkthroughSDD、サンドボックス、Codex、DeepSeek、xAI、Zhipu(GLM)のガイド文書と表示ページを追加・更新し、Provider登録、目次連携、Mermaid表示、レスポンシブUI、検証記録を拡張した。 ChangesAIガイドとHTMLビュー
Next.js Providerページ
Providerナビゲーション
プロジェクト記録
Estimated code review effort: 5 (Critical) | ~120 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 2 | ❌ 3❌ Failed checks (1 warning, 2 inconclusive)
✅ Passed checks (2 passed)
✨ Finishing Touches📝 Generate docstrings
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 10
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Ai-spec-driven-development-markdown-best-practices.html`:
- Around line 957-959: hamburgerBtn の button 要素に type="button"
を明示的に追加し、フォーム内に配置されても送信ボタンとして扱われないようにする。
In `@Google-sandbox-best-practices.html`:
- Around line 1373-1404: Consolidate the duplicated anchor-to-H2 traversal used
by sections and hashBySection into the single navLinks.map loop. For each valid
navigation link, resolve the H2 once, add it to sections, and associate it with
the link hash in hashBySection; retain filtering of missing anchors or sections.
- Around line 762-767: この段落の「Sandboxed
API(SAPI)」と「ライブラリ単位」の強調範囲を独立させ、入れ子になっているstrongタグを修正してください。Sandboxed
API(SAPI)の直後で強調を閉じ、中間の説明文は通常表示に戻し、「C/C++のライブラリ単位」のみを別のstrong要素で強調してください。
In `@Google-sandbox-best-practices.md`:
- Around line 1-2: Update the Markdown around every heading in
Google-sandbox-best-practices.md to satisfy MD022 by adding a blank line before
and after each heading, including the adjacent H1 and H2 at the document start
and all other reported heading locations. Preserve the existing heading text and
document content.
- Around line 208-209:
手順2の「まず」と「最初は」の重複表現を解消してください。見出しの「まず動かす」と本文の「最初はライブラリを直接呼び出す」のどちらかを別の自然な表現に置き換え、アンサンドボックス版を先に実装・確認する意味は維持してください。
In `@Openai-codex-agents-multiagent-best-practices.md`:
- Line 234: 独自サブエージェントの配置先を説明する文を更新し、ユーザー単位の `~/.codex/agents/` に加えてプロジェクトルートの
`.codex/agents/`
もTOML配置先として併記してください。後者がチーム共有用の定義に使えることも明記し、名前指定やモデル割り当ての説明は維持してください。
- Around line 127-135: Update the Mermaid flowchart’s configuration resolution
order to show, from highest priority to lowest, MDM settings, system-managed
settings (managed_config.toml/requirements.toml), CLI and -c overrides, user
settings, system settings, and built-in defaults, with administrator-enforced
limits applied last. Replace the current nodes and edges around the
configuration flow so the diagram no longer presents requirements.toml as the
sole late-stage validation step.
- Line 195: Revise the MCP dependency guidance in the surrounding documentation
to state only that dependencies can be declared in agents/openai.yaml. Remove
the claims that Codex automatically installs, configures, or connects to the
server, while preserving the recommendation to declare the dependency.
- Around line 294-303: モデル選定図と直後の設定説明を、現行推奨に合わせて更新してください。曖昧・多段階・要検証の分岐は
gpt-5.6、バランス・速度重視の分岐は gpt-5.6-terra を示し、旧モデル名と Cerebras の説明を削除してください。個別設定の参照は
agents.<name>.config_file ではなく、各 config.toml の agents.default_subagent_model
を確認する内容に変更してください。
- Line 156:
設定表（Openai-codex-agents-multiagent-best-practices.md:156-156）、説明（同:246-246）、チェックリスト（同:325-325）の3箇所で、現行キーをagents.max_concurrent_threads_per_sessionとして統一し、agents.max_threadsはそのレガシー別名として明記してください。あわせてagents.max_depthはV1でのみ有効でV2では無視されることを各箇所に反映し、agents.max_threadsを現行キーとして扱う記述を修正してください。
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: cb728e55-03f4-4c1f-90df-f78abf12f7e5
📒 Files selected for processing (9)
Ai-spec-driven-development-markdown-best-practices.htmlAi-spec-driven-development-markdown-best-practices.mdAntigravity-cli-guide.mdGemini-multi-agent-best-practices.mdGoogle-sandbox-best-practices.htmlGoogle-sandbox-best-practices.mdHarness-engineering-google-guide.mdOpenai-codex-agents-multiagent-best-practices.mddocs/PROGRESS.md
💤 Files with no reviewable changes (3)
- Harness-engineering-google-guide.md
- Gemini-multi-agent-best-practices.md
- Antigravity-cli-guide.md
…andbox-best-practices.html
…d archive/md/OpenAI
…cit space and min-height
…ices under Providers nav
…onstraints, update MCP docs
…lls loop and TocObserver targets
Contributor
There was a problem hiding this comment.
Actionable comments posted: 6
♻️ Duplicate comments (1)
web-next/app/deepseek/llm-best-practices/page.tsx (1)
63-65: 🩺 Stability & Availability | 🟡 Minor | ⚡ Quick win
DIAGRAM_3内で<br>と<br/>が混在しています。64行目は
<br>を2箇所使用していますが、同じダイアグラム内の65行目は<br/>です。Mermaidのバージョン依存でパース/描画結果が変わるリスクがあるため、<br/>に統一してください（DIAGRAM_4/7/8は既に統一済みです）。🐛 修正案
- Start["タスクの発生"] --> Q1{"高い推論能力<br>（数学・難解なコード・論理パズル）<br>が必須？"} + Start["タスクの発生"] --> Q1{"高い推論能力<br/>（数学・難解なコード・論理パズル）<br/>が必須？"}🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@web-next/app/deepseek/llm-best-practices/page.tsx` around lines 63 - 65, Update the DIAGRAM_3 template string so every HTML line break uses the self-closing <br/> form, replacing the two <br> occurrences while preserving the diagram text and structure.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Google-sandbox-best-practices.html`:
- Line 636: Update the sidebar toggle button identified by sidebarToggle to
explicitly use type="button", and add aria-controls referencing the existing
sidebar element ID; ensure the referenced sidebar has a matching id if needed.
In `@Openai-codex-best-practices-2026.html`:
- Line 793: Update the navToggle button element to explicitly set type="button",
preserving its existing id, aria-label, and displayed text while preventing
default form submission behavior.
- Around line 2340-2345: Update the Mermaid render error handling in the catch
block to insert the user-visible error message through textContent rather than
concatenating err.message into target.innerHTML. Preserve the existing Japanese
prefix and fallback from err.message to err, while keeping the console.error
call unchanged.
- Around line 2364-2370: Update the mobile TOC toggle logic around navToggle and
tocNav so each open-state change synchronizes navToggle’s aria-expanded and
state-dependent aria-label, including resetting both when a TOC link closes the
menu; track the resulting isOpen state consistently. Also update nav.toc styles
at Openai-codex-best-practices-2026.html lines 760-765 to use visibility:hidden
and pointer-events:none when closed, restoring visibility:visible and
pointer-events:auto under nav.toc.open.
In `@Openai-codex-best-practices-2026.md`:
- Around line 194-214: 設定デフォルト階層の図と表を修正し、`.codex/config.toml`（プロジェクト設定）を
`~/.codex/config.toml`（ユーザー設定）より上位に並べ、続けてシステム設定を配置してください。あわせて、フローの矢印が優先度の低下または後続レイヤーによる上書きを示すことを本文で明記し、CLI設定や管理設定との説明もこの順序と矛盾しないよう更新してください。
In `@web-next/app/claude/skill-guide-intermediate/page.tsx`:
- Around line 188-189: Update the h2 content containing “Progressive Disclosure
— Skillのアーキテクチャ” to use an explicit JSX line break, such as br, between the
intended lines so the heading reliably renders on two lines without relying on
source formatting.
---
Duplicate comments:
In `@web-next/app/deepseek/llm-best-practices/page.tsx`:
- Around line 63-65: Update the DIAGRAM_3 template string so every HTML line
break uses the self-closing <br/> form, replacing the two <br> occurrences while
preserving the diagram text and structure.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 135f5f09-8439-434b-9409-f8b5755e495f
📒 Files selected for processing (22)
Ai-spec-driven-development-markdown-best-practices.htmlGoogle-sandbox-best-practices.htmlOpenai-codex-best-practices-2026.htmlOpenai-codex-best-practices-2026.mdarchive/html/OpenAI/Openai-codex-agents-multiagent-best-practices.htmlarchive/html/xAI/Xai-grok-best-practices-intermediate.htmlweb-next/app/claude/skill-guide-intermediate/page.tsxweb-next/app/codex/agent/SidebarToggle.tsxweb-next/app/codex/agent/TocObserver.tsxweb-next/app/codex/agent/page.module.cssweb-next/app/deepseek/llm-best-practices/TocObserver.tsxweb-next/app/deepseek/llm-best-practices/page.module.cssweb-next/app/deepseek/llm-best-practices/page.tsxweb-next/app/xai/grok-best-practices-intermediate/SidebarToggle.tsxweb-next/app/xai/grok-best-practices-intermediate/page.module.cssweb-next/app/xai/grok-best-practices-intermediate/page.tsxweb-next/app/xai/grok-best-practices/page.test.tsxweb-next/app/xai/grok-best-practices/page.tsxweb-next/app/zhipu/zai-glm-best-practices/page.module.cssweb-next/app/zhipu/zai-glm-best-practices/page.test.tsxweb-next/app/zhipu/zai-glm-best-practices/page.tsxweb-next/components/docs/TocObserver.tsx
…nd navToggle aria sync
…config above user config
…AM_3 template string
Contributor
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (3)
web-next/app/deepseek/llm-best-practices/page.tsx (3)
419-425: 🔒 Security & Privacy | 🟡 Minor | ⚡ Quick winAPIキー例を環境変数から読み込む形に統一してください。
api_key="your_deepseek_api_key"は、直前の環境変数設定およびLine 466〜469のベストプラクティスと矛盾します。os.environ["DEEPSEEK_API_KEY"]を使う例に変更してください。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@web-next/app/deepseek/llm-best-practices/page.tsx` around lines 419 - 425, OpenAI client initialization in the DeepSeek example uses a hardcoded API key; replace the api_key value with os.environ["DEEPSEEK_API_KEY"], matching the preceding environment-variable setup and the best-practice example around lines 466–469.
735-825: 🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy liftTool Callsの実行・結果返却・再リクエストまで例に含めてください。
現在のコードはツール定義を送信するだけで、
tool_callsの検出、許可済み関数の実行、role: "tool"の結果追加、最終回答取得の再呼び出しがありません。本文と図が説明する基本フローを実際に実装できるサンプルにしてください。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@web-next/app/deepseek/llm-best-practices/page.tsx` around lines 735 - 825, 実装例のtools定義とclient.chat.completions.create呼び出しを拡張し、初回応答のtool_callsを検出して許可済みのget_weatherを実行し、各結果をrole: "tool"のメッセージとしてmessagesへ追加してください。その後、更新したmessagesとtoolsを使って再度client.chat.completions.createを呼び出し、最終回答を取得する一連のフローまで含めてください。
333-341: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win廃止後の文脈に合わせて、廃止済みであることを伝える案内にしてください。
2026年7月24日は廃止期限を過ぎているため、現在も「予告」「廃止前」が続く書き方は読み手を誤らせます。廃止済み扱いで「旧モデル名は既に利用できず〜」のような表現に言い換えてください。
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@web-next/app/deepseek/llm-best-practices/page.tsx` around lines 333 - 341, Update the warning callout in the llm-best-practices page to describe deepseek-chat and deepseek-reasoner as already discontinued rather than presenting a future deprecation notice. Replace the title and body wording with language stating that the legacy aliases are no longer available, while preserving the recommended deepseek-v4-flash and deepseek-v4-pro models.
♻️ Duplicate comments (1)
Openai-codex-best-practices-2026.md (1)
196-214: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick winManaged Defaults と通常の設定解決順を分離してください。
managed_config.tomlは CLI の--configより優先する管理済み既定値ですが、現状は CLI を最優先としつつ、Managed Defaults の図へプロジェクト・ユーザー・システム設定を混在させています。通常設定はCLI → trusted project → profile → user → system → built-in、managed defaults はMDM → managed_config.toml → user base configとして別表・別図にしてください。Line 231 の役割分担もこの区別に合わせて更新してください。(developers.openai.com)Also applies to: 231-231
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Openai-codex-best-practices-2026.md` around lines 196 - 214, 設定優先順位の説明を、通常の設定解決と Managed Defaults に分離して更新してください。通常設定は CLI → trusted project → profile → user → system → built-in、Managed Defaults は MDM → managed_config.toml → user base config の別図・別表で示し、managed_config.toml が CLI の --config より優先される関係を明記してください。該当する優先順位の図表と、Line 231 の役割分担説明をこの区別に合わせて修正してください。
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@web-next/app/deepseek/llm-best-practices/page.tsx`:
- Around line 419-425: OpenAI client initialization in the DeepSeek example uses
a hardcoded API key; replace the api_key value with
os.environ["DEEPSEEK_API_KEY"], matching the preceding environment-variable
setup and the best-practice example around lines 466–469.
- Around line 735-825:
実装例のtools定義とclient.chat.completions.create呼び出しを拡張し、初回応答のtool_callsを検出して許可済みのget_weatherを実行し、各結果をrole:
"tool"のメッセージとしてmessagesへ追加してください。その後、更新したmessagesとtoolsを使って再度client.chat.completions.createを呼び出し、最終回答を取得する一連のフローまで含めてください。
- Around line 333-341: Update the warning callout in the llm-best-practices page
to describe deepseek-chat and deepseek-reasoner as already discontinued rather
than presenting a future deprecation notice. Replace the title and body wording
with language stating that the legacy aliases are no longer available, while
preserving the recommended deepseek-v4-flash and deepseek-v4-pro models.
---
Duplicate comments:
In `@Openai-codex-best-practices-2026.md`:
- Around line 196-214: 設定優先順位の説明を、通常の設定解決と Managed Defaults に分離して更新してください。通常設定は
CLI → trusted project → profile → user → system → built-in、Managed Defaults は
MDM → managed_config.toml → user base config の別図・別表で示し、managed_config.toml が CLI
の --config より優先される関係を明記してください。該当する優先順位の図表と、Line 231 の役割分担説明をこの区別に合わせて修正してください。
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: bfc65ea9-0c9e-4c33-9b27-4036fe810808
📒 Files selected for processing (5)
Google-sandbox-best-practices.htmlOpenai-codex-best-practices-2026.htmlOpenai-codex-best-practices-2026.mdweb-next/app/claude/skill-guide-intermediate/page.tsxweb-next/app/deepseek/llm-best-practices/page.tsx
Contributor
There was a problem hiding this comment.
♻️ Duplicate comments (1)
Openai-codex-best-practices-2026.md (1)
196-214: 🎯 Functional Correctness | 🟠 Major | ⚡ Quick winManaged Defaults と通常設定の優先順位を混在させないでください。
本文は CLI を最優先としていますが、図では
managed_config.toml/MDM と同じ連鎖に置かれています。現行仕様では managed defaults は CLI を含む通常設定より優先されます。通常設定（CLI → project → profile → user → system → defaults）と、その上位の managed defaults（MDM →managed_config.toml→ 通常設定）を分けて示してください。(developers.openai.com)OpenAI Codex managed_config.toml の優先順位と CLI --config、.codex/config.toml、profile、requirements.toml の関係（公式ドキュメント）🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@Openai-codex-best-practices-2026.md` around lines 196 - 214, 設定優先順位の説明を、通常設定と managed defaults に分離して更新してください。通常設定は CLI → project → profile → user → system → built-in defaults の順に示し、MDM → managed_config.toml は CLI を含むすべての通常設定より上位の制約・既定値として別系統で示してください。本文、Mermaid図、表の説明がこの優先関係と整合し、managed defaults が通常設定の連鎖に混在しないよう修正してください。
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Duplicate comments:
In `@Openai-codex-best-practices-2026.md`:
- Around line 196-214: 設定優先順位の説明を、通常設定と managed defaults に分離して更新してください。通常設定は CLI
→ project → profile → user → system → built-in defaults の順に示し、MDM →
managed_config.toml は CLI
を含むすべての通常設定より上位の制約・既定値として別系統で示してください。本文、Mermaid図、表の説明がこの優先関係と整合し、managed
defaults が通常設定の連鎖に混在しないよう修正してください。
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: e95e735c-b294-42c3-aa71-2309ff97f444
📒 Files selected for processing (5)
Google-sandbox-best-practices.htmlOpenai-codex-best-practices-2026.htmlOpenai-codex-best-practices-2026.mdweb-next/app/claude/skill-guide-intermediate/page.tsxweb-next/app/deepseek/llm-best-practices/page.tsx
…andbox-best-practices.md
…et, and discontinued model status
Contributor
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@web-next/app/deepseek/llm-best-practices/page.tsx`:
- Around line 835-883: Update the tool-call handling around msg.tool_calls so
direct model responses are also displayed: add an else branch that prints
msg.content when no tool calls are present, while keeping the existing
final_resp creation and print flow for tool-call responses.
- Around line 334-339: ページ内の旧モデル廃止日表記を一貫させてください。calloutTitle
と同じ「2026年7月24日廃止済み」の状態に合わせ、最終更新日を2026年7月30日に更新し、タイムラインの「廃止予定」および移行チェックリストの「廃止前に検証」を廃止後の内容へ変更してください。
- Around line 845-849: Update the tool-call example around the get_weather
invocation to parse tool_call.function.arguments as JSON and pass its requested
location value to get_weather instead of the hard-coded "杭州" string. Preserve
the existing get_weather name check and displayed code formatting.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 406e563d-ad81-4ce9-bfb3-a0dfe95e5754
📒 Files selected for processing (4)
Google-sandbox-best-practices.mdOpenai-codex-best-practices-2026.mdarchive/md/OpenAI/Openai-codex-agents-multiagent-best-practices.mdweb-next/app/deepseek/llm-best-practices/page.tsx
…l-call JSON parsing example
Owner
Author
|
@coderabbitai review |
Contributor
✅ Action performedReview finished.
|
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@web-next/app/deepseek/llm-best-practices/page.tsx`:
- Around line 852-855: Validate the parsed tool arguments before invoking
get_weather: handle JSON parsing failures, reject null or array/non-object
values, and require location to be a non-empty string. Update the tool-call flow
around json.loads and get_weather to avoid exceptions or passing None, and
handle invalid arguments through the page’s existing error path.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 0a09da1c-8169-4477-a9b3-879d4f839451
📒 Files selected for processing (1)
web-next/app/deepseek/llm-best-practices/page.tsx
Owner
Author
|
@coderabbitai review |
Contributor
✅ Action performedReview finished.
|
myoshi2891
changed the title
Contributor
|
Note Docstrings generation - SUCCESS |
Docstrings generation was requested by @myoshi2891. * #133 (comment) The following files were modified: * `web-next/app/codex/agent/SidebarToggle.tsx` * `web-next/app/codex/agent/TocObserver.tsx` * `web-next/app/codex/agent/page.tsx` * `web-next/app/deepseek/llm-best-practices/TocObserver.tsx` * `web-next/app/deepseek/llm-best-practices/page.tsx` * `web-next/app/xai/grok-best-practices-intermediate/SidebarToggle.tsx` * `web-next/app/xai/grok-best-practices-intermediate/TocObserver.tsx` * `web-next/app/xai/grok-best-practices-intermediate/page.tsx` * `web-next/app/xai/grok-best-practices/page.tsx` * `web-next/app/zhipu/zai-glm-best-practices/SidebarToggle.tsx` * `web-next/app/zhipu/zai-glm-best-practices/page.tsx`
Merged
📝 Add docstrings to `dev`
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
主に各種 AI プロバイダー・開発ガイドの Next.js App Router への TDD 移植・新規構築と、全ページにわたるアクセシビリティ（a11y）および JSX/Mermaid 描画の修正、さらに DeepSeek や OpenAI Codex などの技術ドキュメント・コード例の精度向上 が行われました。
主要な変更内容
1. ガイドページの Next.js App Router への移植 & 新規実装 (TDD)
/codex/agentページを OpenAI Codex マルチエージェントベストプラクティスガイドに刷新・テスト追加。Deepseek-llm.htmlを/deepseek/llm-best-practicesへ移植。コードハイライト追加および Mermaid コンポーネント修正。grok-best-practicesおよびgrok-best-practices-intermediateページを TDD（テスト作成 → 純粋 JSX 移植 → アーカイブ化）で新規構築。zai-glm-best-practicesガイドを純粋 JSX ページへ移植。2. アクセシビリティ (a11y) & UI・描画コンポーネントの修正
type="button"やaria-controls/aria-expanded属性の付与と同期処理の改善。<br>を JSX の自己閉じタグ<br/>へ修正。Mermaid エラーレンダリングのフォールバック強化。3. ドキュメント仕様のアップデート & サンプルコードの堅牢化
tool_callsの JSON パース処理およびget_weather呼び出し前の引数検証（バリデーション）の追加。bun runへ統一。4. コード品質・フォーマット（lint / MD022）対応
Google-sandbox-best-practices.html等における HTML 構造・スクリプトタグ・スタイルのリファクタリング。