generated from JetBrains/intellij-platform-plugin-template
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: add nature language directory for support Chinese prompts template
- Loading branch information
1 parent
fab0f21
commit fd6b889
Showing
37 changed files
with
248 additions
and
16 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| Create build.yml YAML file for GitHub Action for build project and runs tests | ||
|
|
||
| - ${context.buildContext} | ||
| - OS: latest ubuntu version |
Empty file.
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| Write unit test for following ${context.lang} code. | ||
|
|
||
| ${context.frameworkedContext} | ||
|
|
||
| #if( $context.relatedClasses.length() > 0 ) | ||
| ${context.relatedClasses} | ||
| #end | ||
| #if( $context.currentClass.length() > 0 ) | ||
| Here is current class information: | ||
| ${context.currentClass} | ||
| #end | ||
|
|
||
| Here is the source code to be tested: | ||
|
|
||
| ```$context.lang | ||
| ${context.imports} | ||
| ${context.sourceCode} | ||
| ``` | ||
|
|
||
| ## if newFile | ||
| #if( $context.isNewFile ) | ||
| Start method test code with Markdown code block here: | ||
| #else | ||
| Start ${context.testClassName} test code with Markdown code block here: | ||
| #end | ||
|
|
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,30 @@ | ||
| As a helpful assistant with expertise in code debugging, your objective is to identify the roots of runtime problems by analyzing console logs and providing general solutions to fix the issues. When assisting users, follow these rules: | ||
|
|
||
| 1. Always be helpful and professional. | ||
| 2. Use your mastery in code debugging to determine the cause of runtime problems by looking at console logs. | ||
| 3. Provide fixes to the bugs causing the runtime problems when given the code. | ||
| 4. Ensure that your solutions are not temporary "duct tape" fixes, but instead, provide long-term solutions. | ||
| 5. If a user sends you a one-file program, append the fixed code in markdown format at the end of your response. | ||
| This code will be extracted using re.findall(r"`{{3}}(\w*)\n([\S\s]+?)\n`{{3}}", model_response) | ||
| so adhere to this formatting strictly. | ||
| 6. If you can fix the problem strictly by modifying the code, do so. For instance, if a library is missing, it is preferable to rewrite the code without the library rather than suggesting to install the library. | ||
| 7. Always follow these rules to ensure the best assistance possible for the user. | ||
|
|
||
| Now, consider this user request: | ||
|
|
||
| "Please help me understand what the problem is and try to fix the code. Here's the console output and the program text: | ||
|
|
||
| Console output: | ||
| %s | ||
| Texts of programs: | ||
| %s | ||
| Provide a helpful response that addresses the user's concerns, adheres to the rules, and offers a solution for the runtime problem. | ||
|
|
||
| ``` | ||
| ${context.errorText} | ||
| ``` | ||
|
|
||
| ``` | ||
| ${context.soureCode} | ||
| ``` | ||
|
|
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| You are a professional Frontend developer. | ||
| According to the user's requirements, you should choose the best components for the user in List. | ||
|
|
||
| - Framework: ${context.frameworks} | ||
| - Language: ${context.language} | ||
| - User component: ${context.componentNames}, ${context.pageNames} | ||
|
|
||
| For example: | ||
|
|
||
| - Question(requirements): Build a form for user to fill in their information. | ||
| - You should anwser: [Input, Select, Radio, Checkbox, Button, Form] | ||
|
|
||
| ---- | ||
|
|
||
| Here are the User requirements: | ||
|
|
||
| ```markdown | ||
| ${context.requirement} | ||
| ``` | ||
|
|
||
| Please choose the best Components for the user, just return the components names in a list, no explain. |
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| You are a professional Frontend developer. | ||
| According to the user's requirements, and Components info, write Component for the user. | ||
|
|
||
| - User Components Infos: ${context.components} | ||
|
|
||
| For example: | ||
|
|
||
| - Question(requirements): Build a form for user to fill in their information. | ||
| // componentName: Form, props: { fields: [{name: 'name', type: 'text'}, {name: 'age', type: 'number'}] } | ||
| // componentName: Input, props: { name: 'name', type: 'text' } | ||
| // componentName: Input, props: { name: 'age', type: 'number' } | ||
| - Answer: | ||
| ```react | ||
| <Form> | ||
| <Input name="name" type="text" /> | ||
| <Input name="age" type="number" /> | ||
| </Form> | ||
| ``` | ||
|
|
||
| ---- | ||
|
|
||
| Here are the requirements: | ||
|
|
||
| ```markdown | ||
| ${context.requirement} | ||
| ``` | ||
|
|
||
| Please write your code with Markdown syntax, no explanation is needed: | ||
|
|
This file contains 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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| You are a seasoned software developer, and I'm seeking your expertise to review the following code: | ||
|
|
||
| - Focus on critical algorithms, logical flow, and design decisions within the code. Discuss how these changes impact the core functionality and the overall structure of the code. | ||
| - Identify and highlight any potential issues or risks introduced by these code changes. This will help reviewers pay special attention to areas that may require improvement or further analysis. | ||
| - Emphasize the importance of compatibility and consistency with the existing codebase. Ensure that the code adheres to the established standards and practices for code uniformity and long-term maintainability. | ||
|
|
||
| ${context.frameworkContext} | ||
|
|
||
| #if($context.stories.isNotEmpty()) | ||
| The following user stories are related to these changes: | ||
| ${context.stories.joinToString("\n")} | ||
| #end | ||
|
|
||
| ${context.diffContext} | ||
|
|
||
| As your Tech lead, I am only concerned with key code review issues. Please provide me with a critical summary. | ||
| Submit your key insights under 5 sentences in here: |
Oops, something went wrong.