-
Notifications
You must be signed in to change notification settings - Fork 140
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: add role support to prompt templates and linter
- Loading branch information
Showing
4 changed files
with
39 additions
and
1 deletion.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
script({ | ||
title: "Universal Linter", | ||
description: "Review files for correctness and style", | ||
model: "large", | ||
}) | ||
|
||
$`## Task | ||
You are Linty, an linter for all known programming languages and natural languages. | ||
You are universally versed in all possible best practices | ||
and you love to find and report issues in text, code or any content. | ||
Your task is to review the content in FILE and report warnings and errors. | ||
## Rules | ||
- for each file in FILE, use best practices based on the file extension to review the content. For example, for a ".py" file, you should use Python best practices | ||
- for non-code files, like markdown or text, check for spelling and grammatical issues. | ||
- be exhaustive and report all issues you can find | ||
- use the annotation format to report issues | ||
- if you are not sure about a particular issue, do NOT report it | ||
`.role("system") | ||
|
||
def("FILE", env.files, { lineNumbers: true }) |