mirror of
https://github.com/x1xhlol/system-prompts-and-models-of-ai-tools.git
synced 2025-09-13 11:27:23 +00:00
175 lines
8.3 KiB
JSON
175 lines
8.3 KiB
JSON
[
|
|
{
|
|
"type": "function",
|
|
"function": {
|
|
"name": "codebase_search",
|
|
"description": "Find snippets of code from the codebase most relevant to the search query.\nThis is a semantic search tool, so the query should ask for something semantically matching what is needed.\nIf it makes sense to only search in particular directories, please specify them in the target_directories field.\nUnless there is a clear reason to use your own search query, please just reuse the user's exact query with their wording.\nTheir exact wording/phrasing can often be helpful for the semantic search query. Keeping the same exact question format can also be helpful.",
|
|
"parameters": {
|
|
"type": "object",
|
|
"properties": {
|
|
"query": {
|
|
"type": "string",
|
|
"description": "The search query to find relevant code. You should reuse the user's exact query/most recent message with their wording unless there is a clear reason not to."
|
|
},
|
|
"target_directories": {
|
|
"type": "array",
|
|
"items": {
|
|
"type": "string"
|
|
},
|
|
"description": "Glob patterns for directories to search over"
|
|
},
|
|
"explanation": {
|
|
"type": "string",
|
|
"description": "One sentence explanation as to why this tool is being used, and how it contributes to the goal."
|
|
}
|
|
},
|
|
"required": [
|
|
"query"
|
|
]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "function",
|
|
"function": {
|
|
"name": "read_file",
|
|
"description": "Read the contents of a file (and the outline).\n\nWhen using this tool to gather information, it's your responsibility to ensure you have \nthe COMPLETE context. Each time you call this command you should:\n1) Assess if contents viewed are sufficient to proceed with the task.\n2) Take note of lines not shown.\n3) If file contents viewed are insufficient, call the tool again to gather more information.\n4) Note that this call can view at most 250 lines at a time and 200 lines minimum.\n\nIf reading a range of lines is not enough, you may choose to read the entire file.\nReading entire files is often wasteful and slow, especially for large files (i.e. more than a few hundred lines). So you should use this option sparingly.\nReading the entire file is not allowed in most cases. You are only allowed to read the entire file if it has been edited or manually attached to the conversation by the user.",
|
|
"parameters": {
|
|
"type": "object",
|
|
"properties": {
|
|
"target_file": {
|
|
"type": "string",
|
|
"description": "The path of the file to read. You can use either a relative path in the workspace or an absolute path. If an absolute path is provided, it will be preserved as is."
|
|
},
|
|
"should_read_entire_file": {
|
|
"type": "boolean",
|
|
"description": "Whether to read the entire file. Defaults to false."
|
|
},
|
|
"start_line_one_indexed": {
|
|
"type": "integer",
|
|
"description": "The one-indexed line number to start reading from (inclusive)."
|
|
},
|
|
"end_line_one_indexed_inclusive": {
|
|
"type": "integer",
|
|
"description": "The one-indexed line number to end reading at (inclusive)."
|
|
},
|
|
"explanation": {
|
|
"type": "string",
|
|
"description": "One sentence explanation as to why this tool is being used, and how it contributes to the goal."
|
|
}
|
|
},
|
|
"required": [
|
|
"target_file",
|
|
"should_read_entire_file",
|
|
"start_line_one_indexed",
|
|
"end_line_one_indexed_inclusive"
|
|
]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "function",
|
|
"function": {
|
|
"name": "list_dir",
|
|
"description": "List the contents of a directory. The quick tool to use for discovery, before using more targeted tools like semantic search or file reading. Useful to try to understand the file structure before diving deeper into specific files. Can be used to explore the codebase.",
|
|
"parameters": {
|
|
"type": "object",
|
|
"properties": {
|
|
"relative_workspace_path": {
|
|
"type": "string",
|
|
"description": "Path to list contents of, relative to the workspace root."
|
|
},
|
|
"explanation": {
|
|
"type": "string",
|
|
"description": "One sentence explanation as to why this tool is being used, and how it contributes to the goal."
|
|
}
|
|
},
|
|
"required": [
|
|
"relative_workspace_path"
|
|
]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "function",
|
|
"function": {
|
|
"name": "grep_search",
|
|
"description": "Fast text-based regex search that finds exact pattern matches within files or directories, utilizing the ripgrep command for efficient searching.\nResults will be formatted in the style of ripgrep and can be configured to include line numbers and content.\nTo avoid overwhelming output, the results are capped at 50 matches.\nUse the include or exclude patterns to filter the search scope by file type or specific paths.\n\nThis is best for finding exact text matches or regex patterns.\nMore precise than semantic search for finding specific strings or patterns.\nThis is preferred over semantic search when we know the exact symbol/function name/etc. to search in some set of directories/file types.\n\nThe query MUST be a valid regex, so special characters must be escaped.\ne.g. to search for a method call 'foo.bar(', you could use the query '\\bfoo\\.bar\\('.",
|
|
"parameters": {
|
|
"type": "object",
|
|
"properties": {
|
|
"query": {
|
|
"type": "string",
|
|
"description": "The regex pattern to search for"
|
|
},
|
|
"case_sensitive": {
|
|
"type": "boolean",
|
|
"description": "Whether the search should be case sensitive"
|
|
},
|
|
"include_pattern": {
|
|
"type": "string",
|
|
"description": "Glob pattern for files to include (e.g. '*.ts' for TypeScript files)"
|
|
},
|
|
"exclude_pattern": {
|
|
"type": "string",
|
|
"description": "Glob pattern for files to exclude"
|
|
},
|
|
"explanation": {
|
|
"type": "string",
|
|
"description": "One sentence explanation as to why this tool is being used, and how it contributes to the goal."
|
|
}
|
|
},
|
|
"required": [
|
|
"query"
|
|
]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "function",
|
|
"function": {
|
|
"name": "file_search",
|
|
"description": "Fast file search based on fuzzy matching against file path. Use if you know part of the file path but don't know where it's located exactly. Response will be capped to 10 results. Make your query more specific if need to filter results further.",
|
|
"parameters": {
|
|
"type": "object",
|
|
"properties": {
|
|
"query": {
|
|
"type": "string",
|
|
"description": "Fuzzy filename to search for"
|
|
},
|
|
"explanation": {
|
|
"type": "string",
|
|
"description": "One sentence explanation as to why this tool is being used, and how it contributes to the goal."
|
|
}
|
|
},
|
|
"required": [
|
|
"query",
|
|
"explanation"
|
|
]
|
|
}
|
|
}
|
|
},
|
|
{
|
|
"type": "function",
|
|
"function": {
|
|
"name": "web_search",
|
|
"description": "Search the web for real-time information about any topic. Use this tool when you need up-to-date information that might not be available in your training data, or when you need to verify current facts. The search results will include relevant snippets and URLs from web pages. This is particularly useful for questions about current events, technology updates, or any topic that requires recent information.",
|
|
"parameters": {
|
|
"type": "object",
|
|
"required": [
|
|
"search_term"
|
|
],
|
|
"properties": {
|
|
"search_term": {
|
|
"type": "string",
|
|
"description": "The search term to look up on the web. Be specific and include relevant keywords for better results. For technical queries, include version numbers or dates if relevant."
|
|
},
|
|
"explanation": {
|
|
"type": "string",
|
|
"description": "One sentence explanation as to why this tool is being used, and how it contributes to the goal."
|
|
}
|
|
}
|
|
}
|
|
}
|
|
}
|
|
] |