diff --git a/locales/es/CODE_OF_CONDUCT.md b/locales/es/CODE_OF_CONDUCT.md
index 3547e4628b..82fe929eda 100644
--- a/locales/es/CODE_OF_CONDUCT.md
+++ b/locales/es/CODE_OF_CONDUCT.md
@@ -1,76 +1,71 @@
-# Contributor Covenant Code of Conduct
+# Código de Conducta para Contribuyentes
-## Our Pledge
+## Nuestro Compromiso
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+En el interés de fomentar un entorno abierto y acogedor, nosotros como
+contribuyentes y mantenedores nos comprometemos a hacer de la participación en nuestro proyecto y
+nuestra comunidad una experiencia libre de acoso para todos, independientemente de la edad, tamaño corporal,
+discapacidad, etnia, características sexuales, identidad y expresión de género,
+nivel de experiencia, educación, estatus socioeconómico, nacionalidad, apariencia personal,
+raza, religión o identidad y orientación sexual.
-## Our Standards
+## Nuestros Estándares
-Examples of behavior that contributes to creating a positive environment
-include:
+Ejemplos de comportamientos que contribuyen a crear un entorno positivo incluyen:
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+- Uso de un lenguaje acogedor e inclusivo
+- Respeto a diferentes puntos de vista y experiencias
+- Aceptar de manera constructiva las críticas
+- Centrarse en lo que es mejor para la comunidad
+- Mostrar empatía hacia otros miembros de la comunidad
-Examples of unacceptable behavior by participants include:
+Ejemplos de comportamientos inaceptables por parte de los participantes incluyen:
-- The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
- professional setting
+- El uso de lenguaje o imágenes sexualizadas y la atención o avances sexuales no deseados
+- Trollear, comentarios insultantes/despectivos y ataques personales o políticos
+- Acoso público o privado
+- Publicar información privada de otros, como una dirección física o electrónica,
+ sin permiso explícito
+- Otras conductas que podrían considerarse inapropiadas en un entorno profesional
-## Our Responsibilities
+## Nuestras Responsabilidades
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+Los mantenedores del proyecto son responsables de aclarar los estándares de comportamiento aceptable
+y se espera que tomen medidas correctivas apropiadas y justas en respuesta a cualquier
+caso de comportamiento inaceptable.
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+Los mantenedores del proyecto tienen el derecho y la responsabilidad de eliminar, editar o rechazar
+comentarios, commits, código, ediciones de wiki, issues y otras contribuciones que no estén alineadas con este Código de Conducta, o de prohibir temporal o permanentemente a cualquier contribuyente cuyo comportamiento sea inapropiado,
+amenazante, ofensivo o dañino.
-## Scope
+## Alcance
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+Este Código de Conducta se aplica tanto dentro de los espacios del proyecto como en espacios públicos
+cuando una persona representa el proyecto o su comunidad. Ejemplos de
+representación de un proyecto o comunidad incluyen el uso de una dirección de correo electrónico oficial del proyecto,
+publicar en una cuenta oficial de redes sociales o actuar como un representante designado
+en un evento en línea o fuera de línea. La representación de un proyecto puede
+ser definida y clarificada más específicamente por los mantenedores del proyecto.
-## Enforcement
+## Aplicación
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at hi@cline.bot. All complaints
-will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+Los casos de comportamiento abusivo, acosador o inaceptable de otra manera pueden
+ser reportados contactando al equipo del proyecto en hi@cline.bot. Todas las quejas
+serán revisadas e investigadas y resultarán en una respuesta que
+se considere necesaria y apropiada a las circunstancias. El equipo del proyecto está
+obligado a mantener la confidencialidad con respecto al informante de un incidente.
+Más detalles sobre políticas específicas de aplicación pueden ser publicados por separado.
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Los mantenedores del proyecto que no sigan o hagan cumplir el Código de Conducta de buena
+fe pueden enfrentar repercusiones temporales o permanentes según lo determinen otros
+miembros de la dirección del proyecto.
-## Attribution
+## Atribución
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+Este Código de Conducta está adaptado del [Contributor Covenant][homepage], versión 1.4,
+disponible en https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
[homepage]: https://www.contributor-covenant.org
-For answers to common questions about this code of conduct, see
+Respuestas a preguntas frecuentes sobre este Código de Conducta se pueden encontrar en
https://www.contributor-covenant.org/faq
diff --git a/locales/ja/CODE_OF_CONDUCT.md b/locales/ja/CODE_OF_CONDUCT.md
index 3547e4628b..a2c673a94d 100644
--- a/locales/ja/CODE_OF_CONDUCT.md
+++ b/locales/ja/CODE_OF_CONDUCT.md
@@ -1,76 +1,47 @@
-# Contributor Covenant Code of Conduct
+# コントリビューター規約行動規範
-## Our Pledge
+## 我々の誓い
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+オープンで歓迎される環境を育むために、我々はコントリビューターおよびメンテナーとして、年齢、体型、障害、民族、性の特徴、性別のアイデンティティおよび表現、経験のレベル、教育、社会経済的地位、国籍、個人の外見、人種、宗教、または性的アイデンティティおよび指向に関係なく、プロジェクトおよびコミュニティへの参加がハラスメントのない体験となるよう誓います。
-## Our Standards
+## 我々の基準
-Examples of behavior that contributes to creating a positive environment
-include:
+ポジティブな環境を作り出す行動の例としては、以下のものがあります：
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+- 歓迎的で包括的な言葉を使うこと
+- 異なる視点や経験を尊重すること
+- 建設的な批判を優雅に受け入れること
+- コミュニティのために最善を尽くすことに集中すること
+- 他のコミュニティメンバーに対して共感を示すこと
-Examples of unacceptable behavior by participants include:
+参加者による許容できない行動の例としては、以下のものがあります：
-- The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
- professional setting
+- 性的な言葉や画像の使用、望まれない性的関心やアプローチ
+- 荒らし、侮辱的/軽蔑的なコメント、個人的または政治的な攻撃
+- 公的または私的なハラスメント
+- 明示的な許可なしに他人の個人情報（物理的または電子的な住所など）を公開すること
+- プロフェッショナルな環境で不適切と合理的に見なされるその他の行動
-## Our Responsibilities
+## 我々の責任
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+プロジェクトのメンテナーは、許容される行動の基準を明確にする責任があり、不適切な行動の事例に対して適切かつ公平な是正措置を講じることが期待されています。
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+プロジェクトのメンテナーは、この行動規範に沿わないコメント、コミット、コード、ウィキの編集、問題、およびその他の貢献を削除、編集、または拒否する権利と責任を持ち、また、不適切、脅迫的、攻撃的、または有害と見なされるその他の行動を行ったコントリビューターを一時的または永久に禁止する権利と責任を持ちます。
-## Scope
+## 範囲
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+この行動規範は、プロジェクトスペース内およびプロジェクトやコミュニティを代表する個人が公の場で行動する場合に適用されます。プロジェクトやコミュニティを代表する例としては、公式のプロジェクトメールアドレスを使用すること、公式のソーシャルメディアアカウントを通じて投稿すること、またはオンラインまたはオフラインのイベントで任命された代表として行動することが含まれます。プロジェクトの代表としての行動は、プロジェクトのメンテナーによってさらに定義および明確化される場合があります。
-## Enforcement
+## 執行
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at hi@cline.bot. All complaints
-will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+虐待的、嫌がらせ、またはその他の許容できない行動の事例は、プロジェクトチームに hi@cline.bot まで報告することができます。すべての苦情はレビューおよび調査され、状況に応じて必要かつ適切な対応が行われます。プロジェクトチームは、事件の報告者に関する機密性を保持する義務があります。具体的な執行ポリシーの詳細は別途掲載される場合があります。
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+行動規範を誠実に遵守または執行しないプロジェクトのメンテナーは、プロジェクトのリーダーシップの他のメンバーによって一時的または永久的な影響を受ける可能性があります。
-## Attribution
+## 帰属
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+この行動規範は、[Contributor Covenant][homepage] バージョン 1.4 から適応されており、https://www.contributor-covenant.org/version/1/4/code-of-conduct.html で入手できます。
[homepage]: https://www.contributor-covenant.org
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+この行動規範に関する一般的な質問への回答については、https://www.contributor-covenant.org/faq を参照してください。
diff --git a/locales/ja/CONTRIBUTING.md b/locales/ja/CONTRIBUTING.md
index 75edd9ed43..62544e27cb 100644
--- a/locales/ja/CONTRIBUTING.md
+++ b/locales/ja/CONTRIBUTING.md
@@ -1,82 +1,82 @@
-# Contributing to Cline
+# Clineへの貢献
-We're thrilled you're interested in contributing to Cline. Whether you're fixing a bug, adding a feature, or improving our docs, every contribution makes Cline smarter! To keep our community vibrant and welcoming, all members must adhere to our [Code of Conduct](CODE_OF_CONDUCT.md).
+Clineへの貢献に興味をお持ちいただきありがとうございます。
-## Reporting Bugs or Issues
+## バグや問題の報告
-Bug reports help make Cline better for everyone! Before creating a new issue, please [search existing ones](https://github.com/cline/cline/issues) to avoid duplicates. When you're ready to report a bug, head over to our [issues page](https://github.com/cline/cline/issues/new/choose) where you'll find a template to help you with filling out the relevant information.
+バグ報告は、Clineを皆さんにとってより良いものにするために役立ちます！新しい問題を作成する前に、重複を避けるために[既存の問題を検索](https://github.com/cline/cline/issues)してください。バグを報告する準備ができたら、[問題ページ](https://github.com/cline/cline/issues/new/choose)に移動し、関連情報を記入するためのテンプレートをご利用ください。
- 🔐 Important: If you discover a security vulnerability, please use the Github security tool to report it privately.
+ 🔐 重要: セキュリティ脆弱性を発見した場合は、Githubセキュリティツールを使用して非公開で報告してください。
-## Deciding What to Work On
+## 作業内容の決定
-Looking for a good first contribution? Check out issues labeled ["good first issue"](https://github.com/cline/cline/labels/good%20first%20issue) or ["help wanted"](https://github.com/cline/cline/labels/help%20wanted). These are specifically curated for new contributors and areas where we'd love some help!
+最初の貢献をお探しですか？["good first issue"](https://github.com/cline/cline/labels/good%20first%20issue)や["help wanted"](https://github.com/cline/cline/labels/help%20wanted)のラベルが付いた問題をチェックしてください。これらは新しい貢献者向けに特に選ばれたもので、私たちが助けを求めている分野です！
-We also welcome contributions to our [documentation](https://github.com/cline/cline/tree/main/docs)! Whether it's fixing typos, improving existing guides, or creating new educational content - we'd love to build a community-driven repository of resources that helps everyone get the most out of Cline. You can start by diving into `/docs` and looking for areas that need improvement.
+また、[ドキュメント](https://github.com/cline/cline/tree/main/docs)への貢献も歓迎します！誤字の修正、既存のガイドの改善、新しい教育コンテンツの作成など、コミュニティ主導のリソースリポジトリを構築するために皆さんの力をお借りしたいと考えています。`/docs`に飛び込んで、改善が必要な箇所を探してみてください。
-If you're planning to work on a bigger feature, please create a [feature request](https://github.com/cline/cline/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop) first so we can discuss whether it aligns with Cline's vision.
+大きな機能に取り組む予定がある場合は、まず[機能リクエスト](https://github.com/cline/cline/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop)を作成し、それがClineのビジョンに合致するかどうかを議論しましょう。
-## Development Setup
+## 開発環境のセットアップ
-1. **VS Code Extensions**
+1. **VS Code拡張機能**
- - When opening the project, VS Code will prompt you to install recommended extensions
- - These extensions are required for development - please accept all installation prompts
- - If you dismissed the prompts, you can install them manually from the Extensions panel
+ - プロジェクトを開くと、VS Codeは推奨される拡張機能のインストールを促します
+ - これらの拡張機能は開発に必要です - すべてのインストールプロンプトを受け入れてください
+ - プロンプトを閉じた場合は、拡張機能パネルから手動でインストールできます
-2. **Local Development**
- - Run `npm run install:all` to install dependencies
- - Run `npm run test` to run tests locally
- - Before submitting PR, run `npm run format:fix` to format your code
+2. **ローカル開発**
+ - `npm run install:all`を実行して依存関係をインストールします
+ - `npm run test`を実行してローカルでテストを実行します
+ - PRを提出する前に、`npm run format:fix`を実行してコードをフォーマットします
-## Writing and Submitting Code
+## コードの作成と提出
-Anyone can contribute code to Cline, but we ask that you follow these guidelines to ensure your contributions can be smoothly integrated:
+誰でもClineにコードを貢献できますが、貢献がスムーズに統合されるように以下のガイドラインに従ってください：
-1. **Keep Pull Requests Focused**
+1. **プルリクエストを集中させる**
- - Limit PRs to a single feature or bug fix
- - Split larger changes into smaller, related PRs
- - Break changes into logical commits that can be reviewed independently
+ - PRは単一の機能またはバグ修正に限定してください
+ - 大きな変更は小さな関連PRに分割してください
+ - 論理的なコミットに分けて、独立してレビューできるようにしてください
-2. **Code Quality**
+2. **コード品質**
- - Run `npm run lint` to check code style
- - Run `npm run format` to automatically format code
- - All PRs must pass CI checks which include both linting and formatting
- - Address any ESLint warnings or errors before submitting
- - Follow TypeScript best practices and maintain type safety
+ - `npm run lint`を実行してコードスタイルをチェックします
+ - `npm run format`を実行してコードを自動的にフォーマットします
+ - すべてのPRは、リンティングとフォーマットを含むCIチェックに合格する必要があります
+ - 提出前にESLintの警告やエラーをすべて解決してください
+ - TypeScriptのベストプラクティスに従い、型の安全性を維持してください
-3. **Testing**
+3. **テスト**
- - Add tests for new features
- - Run `npm test` to ensure all tests pass
- - Update existing tests if your changes affect them
- - Include both unit tests and integration tests where appropriate
+ - 新しい機能にはテストを追加してください
+ - `npm test`を実行してすべてのテストが合格することを確認してください
+ - 変更が既存のテストに影響を与える場合は、それらを更新してください
+ - 適切な場合には、ユニットテストと統合テストの両方を含めてください
-4. **Commit Guidelines**
+4. **コミットガイドライン**
- - Write clear, descriptive commit messages
- - Use conventional commit format (e.g., "feat:", "fix:", "docs:")
- - Reference relevant issues in commits using #issue-number
+ - 明確で説明的なコミットメッセージを書いてください
+ - 従来のコミット形式（例："feat:", "fix:", "docs:"）を使用してください
+ - コミットで関連する問題を#issue-numberを使用して参照してください
-5. **Before Submitting**
+5. **提出前に**
- - Rebase your branch on the latest main
- - Ensure your branch builds successfully
- - Double-check all tests are passing
- - Review your changes for any debugging code or console logs
+ - 最新のmainにブランチをリベースしてください
+ - ブランチが正常にビルドされることを確認してください
+ - すべてのテストが合格していることを再確認してください
+ - デバッグコードやコンソールログがないか変更を確認してください
-6. **Pull Request Description**
- - Clearly describe what your changes do
- - Include steps to test the changes
- - List any breaking changes
- - Add screenshots for UI changes
+6. **プルリクエストの説明**
+ - 変更内容を明確に説明してください
+ - 変更をテストする手順を含めてください
+ - 破壊的な変更がある場合はリストしてください
+ - UIの変更にはスクリーンショットを追加してください
-## Contribution Agreement
+## 貢献契約
-By submitting a pull request, you agree that your contributions will be licensed under the same license as the project ([Apache 2.0](LICENSE)).
+プルリクエストを提出することで、あなたの貢献がプロジェクトと同じライセンス（[Apache 2.0](LICENSE)）の下でライセンスされることに同意したことになります。
-Remember: Contributing to Cline isn't just about writing code - it's about being part of a community that's shaping the future of AI-assisted development. Let's build something amazing together! 🚀
+覚えておいてください：Clineへの貢献はコードを書くことだけではなく、AI支援開発の未来を形作るコミュニティの一員になることです。一緒に素晴らしいものを作りましょう！🚀
diff --git a/locales/zh-cn/CODE_OF_CONDUCT.md b/locales/zh-cn/CODE_OF_CONDUCT.md
index 3547e4628b..41229538e1 100644
--- a/locales/zh-cn/CODE_OF_CONDUCT.md
+++ b/locales/zh-cn/CODE_OF_CONDUCT.md
@@ -1,76 +1,47 @@
-# Contributor Covenant Code of Conduct
+# 贡献者公约行为准则
-## Our Pledge
+## 我们的承诺
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+为了营造一个开放和欢迎的环境，我们作为贡献者和维护者承诺让我们的项目和社区的参与体验对每个人都无骚扰，无论年龄、体型、残疾、种族、性别特征、性别认同和表达、经验水平、教育程度、社会经济地位、国籍、个人外貌、种族、宗教或性取向。
-## Our Standards
+## 我们的标准
-Examples of behavior that contributes to creating a positive environment
-include:
+有助于创造积极环境的行为示例包括：
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+- 使用欢迎和包容的语言
+- 尊重不同的观点和经验
+- 优雅地接受建设性的批评
+- 专注于对社区最有利的事情
+- 对其他社区成员表现出同理心
-Examples of unacceptable behavior by participants include:
+参与者不可接受的行为示例包括：
-- The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
- professional setting
+- 使用性化语言或图像以及不受欢迎的性关注或挑逗
+- 故意挑衅、侮辱/贬低性评论和个人或政治攻击
+- 公开或私下骚扰
+- 未经明确许可发布他人的私人信息，如物理或电子地址
+- 其他在专业环境中合理认为不适当的行为
-## Our Responsibilities
+## 我们的责任
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+项目维护者有责任澄清可接受行为的标准，并期望对任何不可接受行为采取适当和公平的纠正措施。
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+项目维护者有权利和责任删除、编辑或拒绝与本行为准则不一致的评论、提交、代码、维基编辑、问题和其他贡献，或暂时或永久禁止任何贡献者进行他们认为不适当、威胁、冒犯或有害的其他行为。
-## Scope
+## 适用范围
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+本行为准则适用于项目空间内和公共空间中代表项目或其社区的个人。代表项目或社区的示例包括使用官方项目电子邮件地址，通过官方社交媒体账户发布，或在在线或离线活动中作为指定代表。项目的代表性可能由项目维护者进一步定义和澄清。
-## Enforcement
+## 执行
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at hi@cline.bot. All complaints
-will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+滥用、骚扰或其他不可接受行为的实例可以通过联系项目团队 hi@cline.bot 报告。所有投诉将被审查和调查，并将导致根据情况认为必要和适当的回应。项目团队有义务对事件报告者保密。具体执行政策的详细信息可能会单独发布。
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+未能善意遵守或执行行为准则的项目维护者可能会面临由项目领导的其他成员决定的临时或永久后果。
-## Attribution
+## 归属
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+本行为准则改编自 [贡献者公约][主页]，版本 1.4，可在 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 获取。
-[homepage]: https://www.contributor-covenant.org
+[主页]: https://www.contributor-covenant.org
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+有关此行为准则的常见问题的答案，请参见 https://www.contributor-covenant.org/faq
diff --git a/locales/zh-cn/CONTRIBUTING.md b/locales/zh-cn/CONTRIBUTING.md
index 75edd9ed43..f528d7c33f 100644
--- a/locales/zh-cn/CONTRIBUTING.md
+++ b/locales/zh-cn/CONTRIBUTING.md
@@ -1,82 +1,82 @@
-# Contributing to Cline
+# 贡献到 Cline
-We're thrilled you're interested in contributing to Cline. Whether you're fixing a bug, adding a feature, or improving our docs, every contribution makes Cline smarter! To keep our community vibrant and welcoming, all members must adhere to our [Code of Conduct](CODE_OF_CONDUCT.md).
+我们很高兴您有兴趣为 Cline 做出贡献。无论您是修复错误、添加功能还是改进我们的文档，每一份贡献都让 Cline 更加智能！为了保持我们的社区充满活力和欢迎，所有成员必须遵守我们的[行为准则](CODE_OF_CONDUCT.md)。
-## Reporting Bugs or Issues
+## 报告错误或问题
-Bug reports help make Cline better for everyone! Before creating a new issue, please [search existing ones](https://github.com/cline/cline/issues) to avoid duplicates. When you're ready to report a bug, head over to our [issues page](https://github.com/cline/cline/issues/new/choose) where you'll find a template to help you with filling out the relevant information.
+错误报告有助于让 Cline 对每个人都更好！在创建新问题之前，请先[搜索现有问题](https://github.com/cline/cline/issues)以避免重复。当您准备好报告错误时，请前往我们的[问题页面](https://github.com/cline/cline/issues/new/choose)，在那里您会找到一个模板来帮助您填写相关信息。
- 🔐 Important: If you discover a security vulnerability, please use the Github security tool to report it privately.
+ 🔐 重要：如果您发现安全漏洞，请使用Github 安全工具私下报告。
-## Deciding What to Work On
+## 决定要做什么
-Looking for a good first contribution? Check out issues labeled ["good first issue"](https://github.com/cline/cline/labels/good%20first%20issue) or ["help wanted"](https://github.com/cline/cline/labels/help%20wanted). These are specifically curated for new contributors and areas where we'd love some help!
+寻找一个好的首次贡献？查看标记为["good first issue"](https://github.com/cline/cline/labels/good%20first%20issue)或["help wanted"](https://github.com/cline/cline/labels/help%20wanted)的问题。这些是专门为新贡献者策划的领域，我们非常欢迎您的帮助！
-We also welcome contributions to our [documentation](https://github.com/cline/cline/tree/main/docs)! Whether it's fixing typos, improving existing guides, or creating new educational content - we'd love to build a community-driven repository of resources that helps everyone get the most out of Cline. You can start by diving into `/docs` and looking for areas that need improvement.
+我们也欢迎对我们的[文档](https://github.com/cline/cline/tree/main/docs)做出贡献！无论是修正错别字、改进现有指南，还是创建新的教育内容 - 我们希望建立一个社区驱动的资源库，帮助每个人充分利用 Cline。您可以从深入研究 `/docs` 并寻找需要改进的地方开始。
-If you're planning to work on a bigger feature, please create a [feature request](https://github.com/cline/cline/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop) first so we can discuss whether it aligns with Cline's vision.
+如果您计划开发一个更大的功能，请先创建一个[功能请求](https://github.com/cline/cline/discussions/categories/feature-requests?discussions_q=is%3Aopen+category%3A%22Feature+Requests%22+sort%3Atop)，以便我们讨论它是否符合 Cline 的愿景。
-## Development Setup
+## 开发设置
-1. **VS Code Extensions**
+1. **VS Code 扩展**
- - When opening the project, VS Code will prompt you to install recommended extensions
- - These extensions are required for development - please accept all installation prompts
- - If you dismissed the prompts, you can install them manually from the Extensions panel
+ - 打开项目时，VS Code 会提示您安装推荐的扩展
+ - 这些扩展是开发所必需的 - 请接受所有安装提示
+ - 如果您忽略了提示，可以从扩展面板手动安装它们
-2. **Local Development**
- - Run `npm run install:all` to install dependencies
- - Run `npm run test` to run tests locally
- - Before submitting PR, run `npm run format:fix` to format your code
+2. **本地开发**
+ - 运行 `npm run install:all` 安装依赖项
+ - 运行 `npm run test` 本地运行测试
+ - 提交 PR 之前，运行 `npm run format:fix` 格式化您的代码
-## Writing and Submitting Code
+## 编写和提交代码
-Anyone can contribute code to Cline, but we ask that you follow these guidelines to ensure your contributions can be smoothly integrated:
+任何人都可以为 Cline 贡献代码，但我们要求您遵循以下指南，以确保您的贡献能够顺利集成：
-1. **Keep Pull Requests Focused**
+1. **保持 Pull Request 集中**
- - Limit PRs to a single feature or bug fix
- - Split larger changes into smaller, related PRs
- - Break changes into logical commits that can be reviewed independently
+ - 将 PR 限制为单个功能或错误修复
+ - 将较大的更改拆分为较小的相关 PR
+ - 将更改分为逻辑提交，以便独立审查
-2. **Code Quality**
+2. **代码质量**
- - Run `npm run lint` to check code style
- - Run `npm run format` to automatically format code
- - All PRs must pass CI checks which include both linting and formatting
- - Address any ESLint warnings or errors before submitting
- - Follow TypeScript best practices and maintain type safety
+ - 运行 `npm run lint` 检查代码风格
+ - 运行 `npm run format` 自动格式化代码
+ - 所有 PR 必须通过 CI 检查，包括 lint 和格式化
+ - 提交前解决所有 ESLint 警告或错误
+ - 遵循 TypeScript 最佳实践并保持类型安全
-3. **Testing**
+3. **测试**
- - Add tests for new features
- - Run `npm test` to ensure all tests pass
- - Update existing tests if your changes affect them
- - Include both unit tests and integration tests where appropriate
+ - 为新功能添加测试
+ - 运行 `npm test` 确保所有测试通过
+ - 如果您的更改影响现有测试，请更新它们
+ - 在适当的情况下包括单元测试和集成测试
-4. **Commit Guidelines**
+4. **提交指南**
- - Write clear, descriptive commit messages
- - Use conventional commit format (e.g., "feat:", "fix:", "docs:")
- - Reference relevant issues in commits using #issue-number
+ - 编写清晰、描述性的提交消息
+ - 使用常规提交格式（例如，“feat:”，“fix:”，“docs:”）
+ - 在提交中引用相关问题，使用 #issue-number
-5. **Before Submitting**
+5. **提交前**
- - Rebase your branch on the latest main
- - Ensure your branch builds successfully
- - Double-check all tests are passing
- - Review your changes for any debugging code or console logs
+ - 将您的分支重新基于最新的 main
+ - 确保您的分支成功构建
+ - 仔细检查所有测试是否通过
+ - 检查您的更改是否有任何调试代码或控制台日志
-6. **Pull Request Description**
- - Clearly describe what your changes do
- - Include steps to test the changes
- - List any breaking changes
- - Add screenshots for UI changes
+6. **Pull Request 描述**
+ - 清楚描述您的更改内容
+ - 包括测试更改的步骤
+ - 列出任何重大更改
+ - 对于 UI 更改，添加截图
-## Contribution Agreement
+## 贡献协议
-By submitting a pull request, you agree that your contributions will be licensed under the same license as the project ([Apache 2.0](LICENSE)).
+通过提交 pull request，您同意您的贡献将根据与项目相同的许可证（[Apache 2.0](LICENSE)）进行许可。
-Remember: Contributing to Cline isn't just about writing code - it's about being part of a community that's shaping the future of AI-assisted development. Let's build something amazing together! 🚀
+记住：为 Cline 做贡献不仅仅是编写代码 - 这是成为一个社区的一部分，共同塑造 AI 辅助开发的未来。让我们一起构建一些令人惊叹的东西！🚀
diff --git a/locales/zh-tw/CODE_OF_CONDUCT.md b/locales/zh-tw/CODE_OF_CONDUCT.md
index 3547e4628b..9f8791ecd9 100644
--- a/locales/zh-tw/CODE_OF_CONDUCT.md
+++ b/locales/zh-tw/CODE_OF_CONDUCT.md
@@ -1,76 +1,47 @@
-# Contributor Covenant Code of Conduct
+# 貢獻者公約行為準則
-## Our Pledge
+## 我們的承諾
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
+為了促進一個開放和歡迎的環境，我們作為貢獻者和維護者承諾，使我們的項目和社區的參與對每個人來說都是一個無騷擾的體驗，不論年齡、體型、殘疾、種族、性別特徵、性別認同和表達、經驗水平、教育程度、社會經濟地位、國籍、個人外貌、種族、宗教或性取向。
-## Our Standards
+## 我們的標準
-Examples of behavior that contributes to creating a positive environment
-include:
+有助於創造積極環境的行為示例包括：
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+- 使用歡迎和包容的語言
+- 尊重不同的觀點和經驗
+- 優雅地接受建設性的批評
+- 專注於對社區最有利的事情
+- 對其他社區成員表示同情
-Examples of unacceptable behavior by participants include:
+參與者不可接受的行為示例包括：
-- The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
- professional setting
+- 使用性化語言或圖像以及不受歡迎的性注意或挑逗
+- 騷擾、侮辱/貶低性評論和個人或政治攻擊
+- 公開或私下騷擾
+- 未經明確許可發布他人的私人信息，例如物理或電子地址
+- 其他在專業環境中合理認為不適當的行為
-## Our Responsibilities
+## 我們的責任
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+項目維護者有責任澄清可接受行為的標準，並預期對任何不可接受行為的實例採取適當和公平的糾正行動。
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+項目維護者有權利和責任刪除、編輯或拒絕與本行為準則不符的評論、提交、代碼、維基編輯、問題和其他貢獻，或暫時或永久禁止任何他們認為不適當、威脅、冒犯或有害的貢獻者。
-## Scope
+## 範圍
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+此行為準則適用於項目空間內以及當個人代表項目或其社區時的公共空間。代表項目或社區的示例包括使用官方項目電子郵件地址、通過官方社交媒體帳戶發布或作為在線或離線活動的指定代表。項目的代表可能由項目維護者進一步定義和澄清。
-## Enforcement
+## 執行
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at hi@cline.bot. All complaints
-will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+濫用、騷擾或其他不可接受行為的實例可以通過聯繫項目團隊 hi@cline.bot 來報告。所有投訴將被審查和調查，並將根據情況作出必要和適當的回應。項目團隊有義務對事件的報告者保密。具體執行政策的詳細信息可能會單獨發布。
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+未能善意遵循或執行行為準則的項目維護者可能會面臨由項目領導層其他成員決定的暫時或永久後果。
-## Attribution
+## 歸屬
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+此行為準則改編自 [Contributor Covenant][homepage]，版本 1.4，可在 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html 獲得。
[homepage]: https://www.contributor-covenant.org
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq
+有關此行為準則的常見問題的答案，請參見 https://www.contributor-covenant.org/faq