Skip to content

Commit d79bfa3

Browse files
Typo in graph
* update to logseq graph
1 parent e96395b commit d79bfa3

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

graphs/prompts/pages/Tools.md

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ By adding tools to prompts during the [authoring process]([[Authoring Prompts]])
5757

5858
When defining a `prompt` type tool, the parameters will be available to be interpolated into the prompt definition before being sent to the model. For example, the above function definition has parameters `code` and `violation` so the prompt file itself can reference those using moustache template syntax. For example the prompt file reference above could look like the file below (note the reference `{{code}}` and `{{violation}}` )
5959

60-
```
60+
```markdown
6161
# prompt user
6262

6363
## Original Code
@@ -70,9 +70,10 @@ By adding tools to prompts during the [authoring process]([[Authoring Prompts]])
7070
**STRICTLY FOLLOW THE RULES BELOW:**
7171
generate new code which will resolve the violation
7272
Return the response in the following format:
73-
```python
73+
`` `python
7474
<corrected code>
75+
`` `
7576
```
76-
77-
Instead of a `ref` in the above definition, users can also define a `prompt-file` which must be a relative path (relative the prompt file that was originally passed to the engine). This `prompt-file` field is useful for developing prompts, because we can use local definitions that have not yet been pushed to git.
78-
```
77+
Instead of a `ref` in the above definition, users can also define a `prompt-file` which
78+
must be a relative path (relative the prompt file that was originally passed
79+
to the engine). This `prompt-file` field is useful for developing prompts, because we can use local definitions that have not yet been pushed to git.

0 commit comments

Comments
 (0)