Skip to content

docs: add sync-zh-en-docs skill#7167

Merged
chenjiahan merged 5 commits intomainfrom
add_doc_skill_0210
Feb 10, 2026
Merged

docs: add sync-zh-en-docs skill#7167
chenjiahan merged 5 commits intomainfrom
add_doc_skill_0210

Conversation

@chenjiahan
Copy link
Member

@chenjiahan chenjiahan commented Feb 10, 2026

Summary

Added a new skill file describing the sync-zh-en-docs skill, including its purpose, usage steps, and formatting instructions.

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).

Copilot AI review requested due to automatic review settings February 10, 2026 08:48
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @chenjiahan, I'm Gemini Code Assist1! 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!

This pull request introduces a new automated skill designed to streamline the process of synchronizing documentation between Chinese and English versions. It provides clear instructions for contributors on how to maintain consistency across localized content, enhancing the efficiency and accuracy of documentation updates. The change also integrates this new skill into the main website's README, making it easily discoverable and actionable for developers.

Highlights

  • New Skill Documentation: A new skill file, sync-zh-en-docs, has been added, detailing its purpose, usage steps, and formatting instructions for synchronizing Chinese and English documentation.
  • README Update: The website/README.md file has been updated to include a reference to the newly added sync-zh-en-docs skill, guiding users on how to utilize it for documentation synchronization.
Changelog
  • .agents/skills/sync-zh-en-docs/SKILL.md
    • Added a new skill definition for sync-zh-en-docs.
  • website/README.md
    • Added a note referencing the new sync-zh-en-docs skill.
Activity
  • The pull request author, chenjiahan, created this PR with a clear description of the changes and their purpose.
  • No further activity such as comments or reviews has been recorded yet.
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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a new skill documentation for synchronizing Chinese and English documents. The changes are well-structured, but I've identified a couple of areas for improvement to enhance clarity and user experience. Specifically, one of the steps in the new skill guide is incomplete, and a reference in the README could be made into a clickable link for easier navigation. My detailed feedback is in the comments below.

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds contributor guidance for keeping the Chinese and English documentation directories in sync by introducing a local “skill” document and referencing it from the website contributing README.

Changes:

  • Mention the sync-zh-en-docs local skill in website/README.md to help contributors sync zh/en docs.
  • Add a new skill definition at .agents/skills/sync-zh-en-docs/SKILL.md describing when/how to sync and format.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
website/README.md Adds a pointer to the new local skill for syncing zh/en documentation.
.agents/skills/sync-zh-en-docs/SKILL.md Introduces the skill documentation with steps and a formatting command.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@chenjiahan chenjiahan merged commit 2a2c13b into main Feb 10, 2026
6 checks passed
@chenjiahan chenjiahan deleted the add_doc_skill_0210 branch February 10, 2026 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments