CSGHub prompts

[ymh6315431]

What this PR does:

Which issue(s) this PR fixes:

Fixes #

Type of changes
Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Feature/Issue validation/testing:

Please describe the tests that you ran to verify your changes and relevant result summary.

• Test A

• Test B

• Logs

Special notes for your reviewer:

Checklist:

• I have added unit/e2e tests that prove your fix is effective or that this feature works.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• I have reviewed my own code and ensured that it follows the project's style guidelines.

Release note:

MR Summary:

The summary is added by @codegpt.

The Merge Request introduces a comprehensive feature set for managing and optimizing prompts within the CSGHub platform. Key updates include:

1. Implemented a new feature for creating, editing, and managing prompts and prompt libraries.
2. Added support for prompt optimization assistance.
3. Integrated prompts with related models, datasets, and codes for enhanced collaboration and usability.
4. Introduced language and tag filters for prompts to facilitate easier navigation and organization.
5. Provided functionalities for public and private visibility settings for prompt libraries.
6. Enabled deletion of prompts and prompt libraries with confirmation steps to prevent accidental data loss.
7. Enhanced the UI with dedicated components for prompts management, including a mobile menu for better accessibility on smaller devices.
8. Updated localization files to support new features in both English and Chinese languages.
9. Registered new routes and handlers for prompt-related operations, ensuring seamless integration with the existing platform infrastructure.

[starship-github]

Linter Issue Report

During the code review, a list issues were found. These issues could affect the code quality, maintainability, and consistency. Below is the detailed Linter issue report:

internal/handlers/render/prompts.go

Lint Issue: undefined: DefaultLicensesJSON

• Location: Line 27, Column 27
• Code Snippet:

  "licenses":      string(DefaultLicensesJSON),

• Suggestion: It appears DefaultLicensesJSON is referenced but not defined within this file or imported packages. Ensure that DefaultLicensesJSON is correctly defined in a package that is imported by this file. If it's meant to be a constant or variable accessible within this scope, you'll need to define it. For example:

  var DefaultLicensesJSON = []byte{/* your JSON data */}

  Or, if it's defined in another package, make sure to import that package correctly at the top of your file.

Lint Issue: undefined: RenderBaseInstance

• Location: Line 30, Column 2
• Code Snippet:

  RenderBaseInstance.RenderTemplate(ctx, "prompts_index", data)

• Suggestion: The RenderBaseInstance seems to be an undefined variable or instance. Ensure that you have a RenderBaseInstance that is properly instantiated from a struct that has the RenderTemplate method. If RenderBaseInstance is supposed to be a global instance, verify that it is correctly defined and imported. For instance:

  var RenderBaseInstance = NewRenderBaseInstance()

Lint Issue: undefined: RenderBaseInstance

• Location: Line 36, Column 2
• Code Snippet:

  RenderBaseInstance.RenderTemplate(ctx, "prompts_assistant", data)

• Suggestion: Similar to the previous issue, RenderBaseInstance is not recognized. Ensure that RenderBaseInstance is defined and accessible in this scope. If it's part of another package, check your imports and the visibility (exported name) of RenderBaseInstance. If it's meant to be defined within this package, ensure it's correctly instantiated before use.

---

Please make the suggested changes to improve the code quality.

[starship-github]

MR Evaluation:

This feature is still under test, evaluation are given by AI and might be inaccurate.

After evaluation, the code changes in the Merge Request get score: 83.

Analysis for the evaluation score:

• The code change may not include corresponding unit tests.
• The code change may not include corresponding integration testing.
• The code change may not include the corresponding user manual.
• The code change may not include the corresponding development documentation.

Tips

CodeReview Commands (invoked as MR or PR comments)

• @codegpt /review to trigger an code review.
• @codegpt /evaluate to trigger code evaluation process.
• @codegpt /describe to regenerate the summary of the MR.
• @codegpt /secscan to scan security vulnerabilities for the MR or the Repository.
• @codegpt /help to get help.

CodeReview Discussion Chat

There are 2 ways to chat with Starship CodeReview:

• Review comments: Directly reply to a review comment made by StarShip.
  Example:
  • @codegpt How to fix this bug?
• Files and specific lines of code (under the "Files changed" tab):
  Tag @codegpt in a new review comment at the desired location with your query.
  Examples:
  • @codegpt generate unit testing code for this code snippet.

Note: Be mindful of the bot's finite context window.
It's strongly recommended to break down tasks such as reading entire modules into smaller chunks.
For a focused discussion, use review comments to chat about specific files and their changes, instead of using the MR/PR comments.

CodeReview Documentation and Community

• Visit our Documentation
  for detailed information on how to use Starship CodeReview.

About Us:

Visit the OpenCSG StarShip website for the Dashboard and detailed information on CodeReview, CodeGen, and other StarShip modules.

[starship-github]

The StarShip CodeReviewer was triggered but terminated because it encountered an issue: The MR state is not opened.

Tips

CodeReview Commands (invoked as MR or PR comments)

• @codegpt /review to trigger an code review.
• @codegpt /evaluate to trigger code evaluation process.
• @codegpt /describe to regenerate the summary of the MR.
• @codegpt /secscan to scan security vulnerabilities for the MR or the Repository.
• @codegpt /help to get help.

CodeReview Discussion Chat

There are 2 ways to chat with Starship CodeReview:

• Review comments: Directly reply to a review comment made by StarShip.
  Example:
  • @codegpt How to fix this bug?
• Files and specific lines of code (under the "Files changed" tab):
  Tag @codegpt in a new review comment at the desired location with your query.
  Examples:
  • @codegpt generate unit testing code for this code snippet.

Note: Be mindful of the bot's finite context window.
It's strongly recommended to break down tasks such as reading entire modules into smaller chunks.
For a focused discussion, use review comments to chat about specific files and their changes, instead of using the MR/PR comments.

CodeReview Documentation and Community

• Visit our Documentation
  for detailed information on how to use Starship CodeReview.