feat: standardize model label naming conventions

[yinxulai]

• Unified all model labels to use proper title case formatting

• Updated the following model labels:

  • deepseek-v3 → DeepSeek V3
  • deepseek-r1 → DeepSeek R1
  • gpt-oss-120b → GPT-OSS 120B
  • gpt-oss-20b → GPT-OSS 20B
  • kimi-k2 → Kimi K2
  • glm-4.5 → GLM-4.5
  • glm-4.5-air → GLM-4.5 Air
  • qwen-turbo → Qwen Turbo
  • qwen3-32b → Qwen3 32B

• Ensures consistency with existing models like Claude and Qwen3 Max Preview

• Improves professional appearance and readability in user interface

[niupilot]

🔍 PR Review Complete ✅

I've thoroughly reviewed PR #15 - Model label standardization changes.

📋 Review Tasks

• Analyze the 9 changed YAML model files
• Verify label formatting consistency
• Check alignment with existing model naming conventions
• Review for potential issues or inconsistencies
• Check if documentation needs updates
• Provide comprehensive review feedback

---

✅ Review Summary

This PR successfully standardizes model labels across 9 YAML configuration files, transforming lowercase/kebab-case labels into proper title case formatting. The changes are well-executed and improve the professional appearance of the UI.

🎯 What This PR Does Well

✅ Consistent Formatting

• All changes follow a consistent title case pattern (e.g., deepseek-v3 → DeepSeek V3)
• Both Chinese (zh_Hans) and English (en_US) labels are updated uniformly
• Each file shows exactly +2/-2 line changes, indicating surgical precision

✅ Alignment with Existing Conventions

• The new format matches existing models like:
  • Claude 4.1 Opus (/workspace/models/llm/claude-4.1-opus.yaml:3-4)
  • Qwen3 Max Preview (/workspace/models/llm/qwen3-max-preview.yaml:3-4)
  • DeepSeek V3.1 (/workspace/models/llm/deepseek-v3.1.yaml:3-4)

✅ Proper Brand Name Handling

• Correctly capitalizes brand names: DeepSeek, GPT-OSS, GLM, Kimi, Qwen
• Maintains appropriate spacing and versioning (e.g., GLM-4.5 Air, GPT-OSS 120B)

🔍 Technical Analysis

File Structure & Impact

• Changes are limited to the label section only (lines 3-4 in each file)
• No modification to core functionality (model, model_type, features, parameter_rules)
• Maintains proper YAML structure and indentation

Scope Coverage
The following models were updated:

• DeepSeek series: deepseek-r1, deepseek-v3
• GLM series: glm-45, glm-45-air
• GPT-OSS series: gpt-oss-120b, gpt-oss-20b
• Others: kimi-k2, qwen-turbo, qwen3-32b

📝 Minor Suggestions

Documentation Sync ⚠️
The README.md lists models with the new naming format (lines 24-30), which suggests this PR completes an ongoing standardization effort. However, I recommend:

1. Verify consistency - Double-check that all model names in the README match the new YAML labels exactly
2. Update examples - If there are any configuration examples or screenshots showing the old labels, they should be updated

Future Considerations 💡

• Consider adding a linting rule or validation script to ensure future model additions follow this naming convention
• The standardization looks complete for the current model set

🏆 Verdict

✅ APPROVED - This is a clean, well-executed standardization effort that:

• Improves user experience with professional label formatting
• Maintains consistency with existing high-quality models
• Makes no breaking changes to functionality
• Follows established patterns in the codebase

The changes are ready to merge and will enhance the plugin's professional appearance in the Dify interface.

👉 Want me to re-run this review? Just type /review in the comments! For more usage examples, visit CodeAgent GitHub Repository.

[gemini-code-assist]

Summary of Changes

Hello @yinxulai, 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!

This pull request aims to improve the user interface's clarity and professionalism by standardizing the naming conventions for various large language model labels. By converting existing labels to a consistent title case format, the change enhances readability and maintains a unified appearance across the platform, aligning with the presentation of other established models.

Highlights

• Standardized Model Labels: All model labels have been unified to follow a consistent title case formatting, improving overall presentation and user experience.
• Specific Model Updates: Nine specific model labels, including DeepSeek V3, DeepSeek R1, GPT-OSS 120B, GPT-OSS 20B, Kimi K2, GLM-4.5, GLM-4.5 Air, Qwen Turbo, and Qwen3 32B, have been updated to reflect the new naming convention.
• Enhanced Readability and Consistency: This change ensures consistency with existing models like Claude and Qwen3 Max Preview, significantly enhancing the professional appearance and readability of model names within the user interface.

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. ↩

[gemini-code-assist]

Code Review

This pull request standardizes the display labels for several language models, improving UI consistency and readability by using title case. The changes are well-executed across all affected model configuration files. I've pointed out a couple of opportunities to improve the Chinese (zh_Hans) labels for the Qwen models to use their native Chinese names, which would enhance the experience for Chinese-speaking users. Otherwise, the changes look good.

[gemini-code-assist]

While standardizing the labels is a good improvement, the zh_Hans label for Qwen models should ideally be in Chinese. 'Qwen' is known as '通义千问' in Chinese. Consider using 通义千问 Turbo for the zh_Hans label to provide a better experience for Chinese-speaking users.

  zh_Hans: 通义千问 Turbo

[gemini-code-assist]

Similar to the other Qwen model, the zh_Hans label should ideally be in Chinese. 'Qwen' is '通义千问'. Consider using 通义千问3 32B for the zh_Hans label to maintain consistency and improve localization.

  zh_Hans: 通义千问3 32B