Created
March 19, 2025 17:33
-
-
Save ondrasek/bdbcda0213498fb9c4c4e58e8c90c4b6 to your computer and use it in GitHub Desktop.
continue.dev config.yaml
This file contains hidden or 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
| name: "Continue Local Config" | |
| version: "1.0" | |
| schema: v1 | |
| models: | |
| - name: Llama 3.1 8B | |
| provider: ollama | |
| model: llama3.1:8b | |
| roles: | |
| - chat | |
| - autocomplete | |
| - edit | |
| - apply | |
| - summarize | |
| - name: qwen2.5-coder 7B | |
| provider: ollama | |
| model: qwen2.5-coder:7b | |
| roles: | |
| - chat | |
| - autocomplete | |
| - edit | |
| - apply | |
| - summarize | |
| - name: qwen2.5-coder 14B | |
| provider: ollama | |
| model: qwen2.5-coder:14b | |
| roles: | |
| - chat | |
| - autocomplete | |
| - edit | |
| - apply | |
| - summarize | |
| - name: qwen2.5-coder 32B | |
| provider: ollama | |
| model: qwen2.5-coder:32b | |
| roles: | |
| - chat | |
| - autocomplete | |
| - edit | |
| - apply | |
| - summarize | |
| - name: codestral | |
| provider: ollama | |
| model: codestral | |
| roles: | |
| - chat | |
| - autocomplete | |
| - edit | |
| - apply | |
| - summarize | |
| - name: phi4 | |
| provider: ollama | |
| model: phi4 | |
| roles: | |
| - chat | |
| - autocomplete | |
| - edit | |
| - apply | |
| - summarize | |
| - name: mistral | |
| provider: ollama | |
| model: mistral | |
| roles: | |
| - chat | |
| - edit | |
| - apply | |
| - summarize | |
| - name: mistral-nemo | |
| provider: ollama | |
| model: mistral-nemo | |
| roles: | |
| - chat | |
| - edit | |
| - apply | |
| - summarize | |
| - name: deepseek-r1 | |
| provider: ollama | |
| model: deepseek-r1 | |
| roles: | |
| - chat | |
| - autocomplete | |
| - edit | |
| - apply | |
| - summarize | |
| - name: starcoder2 3b | |
| provider: ollama | |
| model: starcoder2:3b | |
| roles: | |
| - autocomplete | |
| - name: nomic-embed-text | |
| provider: ollama | |
| model: nomic-embed-text | |
| roles: | |
| - embed | |
| context: | |
| - provider: code | |
| - provider: docs | |
| - provider: diff | |
| - provider: terminal | |
| - provider: problems | |
| - provider: folder | |
| - provider: codebase | |
| - provider: web | |
| - provider: open | |
| - provider: search | |
| - provider: debugger | |
| - provider: repo-map | |
| - provider: commit | |
| params: | |
| Depth: 50 | |
| LastXCommitsDepth: 10 | |
| - provider: currentFile | |
| rules: | |
| - Give concise, short and clear responses. | |
| - Always focus on clean and secure code, avoid code smells. | |
| prompts: | |
| - name: share | |
| description: Export the current chat session to markdown | |
| prompt: | | |
| Take the current chat session, convert it into github style markdown and export it. | |
| - name: cmd | |
| description: Generate a shell command | |
| prompt: | | |
| Create a shell command for zsh shell from the provided context. | |
| - name: commit | |
| description: Generate a git commit message | |
| prompt: | | |
| Create a commit message from the provided context. The message must be short, but summarize | |
| the changes made in the codebase. | |
| - name: review | |
| description: Review the provided code | |
| prompt: | | |
| Review the provided code and check for any mistakes. You must look for: | |
| - Syntax Errors | |
| - Logic Errors | |
| - Security Vulnerabilities | |
| - Memory Leaks | |
| - Code Smells | |
| - Deprecated or Obsolete APIs or Features | |
| - Non-idiomatic Language Expressions | |
| - name: test | |
| description: Unit test a function | |
| prompt: | | |
| Please write a complete suite of unit tests for this function. You should use the Jest testing framework. The tests should cover all possible edge cases and should be as thorough as possible. You should also include a description of each test case. | |
| - name: document | |
| description: Write a documentation for the provided context | |
| prompt: | | |
| Please write a meaningful documentation for the provided code. If the code contains more than one unit, i.e. more than one function, module, class or method, document each such unit separately. The documentation must include intent and the nature of the implementation, identify edge cases and point out any complexities. You shall also add code comments to specific lines which seem difficult to read or understand. All documentation must be in the form of code comments. You can also use mermaid or puml diagrams if it helps clarity, but they also must be embedded withing code comments. | |
| - name: refactor | |
| description: Refactor the provided code | |
| prompt: | | |
| Please refactor the provided code. The refactoring should be done in such a way that it improves the readability, maintainability, and performance of the code. You should also ensure that the refactored code is backward compatible with the original code. | |
| - name: arch-kata | |
| description: Architectural Kata with AI Coach | |
| prompt: | | |
| You will generate a description of a software architecture of a hypothetical random software system. The description should be rather detailed, refer to architectural styles, communication patterns and explain how does | |
| it address security, reliablity and scalability concerns. However, you will make deliberate mistakes in the | |
| architecture of this system. You will not reveal these mistakes to me. You will challenge me with questions and my goal is to identify these mistakes. You will provide feedback on my answers and guide me towards the correct solution. Under any circumstances, you will not generate any code snippets. You will communicate in natural language only. You will have no affinity towards a particular technology or an architectural style. You will consider at least the following architectural styles: microservices, modular monolith, layered (n-tier) architecture, event-driven architecture, serverless architecture, big ball of mud and distributed monolith. You will not reveal the particular architectural style and let me determine it myself. | |
| - name: codebase-arch-kata | |
| description: Architectural Kata with AI Coach from my current codebase | |
| prompt: | | |
| Using @repo-map and @open, you will generate a description of a software architecture of this software system. The description should be rather detailed, refer to architectural styles, communication patterns and explain how does it address security, reliablity and scalability concerns. However, you will make deliberate mistakes in the architecture of this system. You will not reveal these mistakes to me. You will challenge me with questions and my goal is to identify these mistakes. You will provide feedback on my answers and guide me towards the correct solution. Under any circumstances, you will not generate any code snippets. You will communicate in natural language only. You will have no affinity towards a particular technology or an architectural style. You will consider at least the following architectural styles: microservices, modular monolith, layered (n-tier) architecture, event-driven architecture, serverless architecture, big ball of mud and distributed monolith. You will not reveal the particular architectural style and let me determine it myself. | |
| - name: arch | |
| description: Describe Architecture | |
| prompt: | | |
| Using @repo-map and @open, you will generate a description of a software architecture of this software system. The description should be rather detailed, refer to architectural styles, communication patterns and explain how does it address security, reliablity and scalability concerns. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment