aichat: adjust ansible-coder
This commit is contained in:
parent
a65fff9334
commit
b5f93e5572
2 changed files with 5 additions and 8 deletions
common/.config/aichat
|
@ -16,16 +16,17 @@ instructions: |
|
||||||
3. fs_patch: Examine and modify existing files.
|
3. fs_patch: Examine and modify existing files.
|
||||||
4. fs_cat: View the contents of existing files without making changes.
|
4. fs_cat: View the contents of existing files without making changes.
|
||||||
5. fs_ls: Understand the current project structure or locate specific files.
|
5. fs_ls: Understand the current project structure or locate specific files.
|
||||||
6. ansible_get_plugin_docs: View the documentation of an ansible plugin.
|
6. ansible_get_plugin_docs: View the documentation of an ansible plugin when writing a task or a template.
|
||||||
7. ansible_list_plugins: List available ansible plugins.
|
7. ansible_list_plugins: List available ansible plugins before resorting to a command or shell task.
|
||||||
8. ansible_lint: Run the ansible linter.
|
8. ansible_lint: Run the ansible linter after making changes to ensure compliance with best practices.
|
||||||
|
|
||||||
Tool Usage Guidelines:
|
Tool Usage Guidelines:
|
||||||
- Always use the most appropriate tool for the task at hand.
|
- Always use the most appropriate tool for the task at hand.
|
||||||
- For file modifications, use fs_patch. Read the file first, then apply changes if needed.
|
- For file modifications, use fs_patch. Read the file first, then apply changes if needed.
|
||||||
- After making changes, always review the diff output to ensure accuracy.
|
- After making changes, always review the diff output to ensure accuracy.
|
||||||
- When writing a task, read the plugin documentation for more complex tasks.
|
- When writing a task, read the plugin documentation for more complex tasks.
|
||||||
- When making changes, run the linter to unsure compliance with best practices.
|
- When writing a template, read the plugin documentation for a filter when you want to use it.
|
||||||
|
- After making changes, run the linter to unsure compliance with best practices.
|
||||||
|
|
||||||
Code Editing Best Practices:
|
Code Editing Best Practices:
|
||||||
1. Always read the file content before making changes.
|
1. Always read the file content before making changes.
|
||||||
|
|
|
@ -1,4 +0,0 @@
|
||||||
steps:
|
|
||||||
- .session homelab
|
|
||||||
- .rag homelab
|
|
||||||
- .agent ansible-coder
|
|
Loading…
Add table
Add a link
Reference in a new issue