janus-llm 4.3.1__py3-none-any.whl → 4.4.5__py3-none-any.whl

janus/parsers/uml.py

@@ -3,10 +3,10 @@ import subprocess  # nosec
 from pathlib import Path
 from tempfile import NamedTemporaryFile
 
-from langchain_core.exceptions import OutputParserException
 from langchain_core.messages import BaseMessage
 
 from janus.parsers.code_parser import CodeParser
+from janus.parsers.parser import JanusParserException
 from janus.utils.logger import create_logger
 
 log = create_logger(__name__)
@@ -14,6 +14,7 @@ log = create_logger(__name__)
 
 class UMLSyntaxParser(CodeParser):
     def _check_plantuml(self, text: str) -> None:
+        original_text = text
         # Leading newlines can break the parser, remove them
         text = text.replace("\\n", "\n").strip()
 
@@ -43,7 +44,7 @@ class UMLSyntaxParser(CodeParser):
             log.error(err_txt)
             raise Exception(err_txt)
 
-        # Check for bad outputs, raise OutputParserExceptions if so
+        # Check for bad outputs, raise JanusParserExceptions if so
         if "Error" in stderr or "Error" in stdout:
             err_txt = "Recieved UML parsing error(s)."
 
@@ -64,7 +65,7 @@ class UMLSyntaxParser(CodeParser):
                 err_txt += f"\nError located at line {i} must be fixed:\n"
                 err_txt += "\n".join(err_lines)
             log.warning(err_txt)
-            raise OutputParserException(err_txt)
+            raise JanusParserException(original_text, err_txt)
 
         if "Warning" in stdout or "Warning" in stderr:
             err_txt = "Recieved UML parsing warning (often due to missing PLANTUML)."
@@ -74,7 +75,7 @@ class UMLSyntaxParser(CodeParser):
                 err_txt += f"\nSTDOUT:\n```\n{stdout.strip()}\n```\n"
 
             log.warning(err_txt)
-            raise OutputParserException(err_txt)
+            raise JanusParserException(original_text, err_txt)
 
     def _get_error_lines(self, s: str) -> list[int]:
         return [int(x.group(1)) for x in re.finditer(r"Error line (\d+) in file:", s)]

janus/prompts/prompt.py

@@ -23,7 +23,7 @@ TEXT_OUTPUT = []
 # same language as the input, regardless of the `output-lang` argument.
 SAME_OUTPUT = ["document_inline"]
 
-JSON_OUTPUT = ["evaluate", "document", "document_madlibs", "requirements"]
+JSON_OUTPUT = ["evaluate", "document", "document_cloze", "requirements"]
 
 # Directory containing Janus prompt template directories and files
 JANUS_PROMPT_TEMPLATES_DIR = Path(__file__).parent / "templates"
@@ -109,7 +109,7 @@ class PromptEngine(ABC):
         source_language = source_language.lower()
         self.variables = dict(
             SOURCE_LANGUAGE=source_language,
-            FILE_SUFFIX=LANGUAGES[source_language]["suffix"],
+            FILE_SUFFIX=LANGUAGES[source_language]["suffixes"],
             SOURCE_CODE_EXAMPLE=LANGUAGES[source_language]["example"],
         )
         if target_language is not None:

janus/prompts/templates/README.md

@@ -0,0 +1,30 @@
+# Prompt Template Files
+
+Janus supports defining custom prompts in text files.
+
+```
+directory_name/
+    system.txt
+    human.txt
+    variables.json (optional)
+```
+
+## Prompt templates
+- `system.txt` contains text representing the system prompt template,
+  + Ex. "Your purpose is to understand {SOURCE_LANGUAGE} code."
+- `human.txt` contains text representing the human prompt template.
+  + Ex. "Summarize the contents of the following {SOURCE_LANGUAGE} code in {written_language} sentences.
+
+Both prompt templates can make use of f-string-style arguments, i.e. `{VARIABLE}`. Multiple lines are supported.
+
+To reuse a prompt, say for the same system directive with differing output styles, create a symbolic link to the original file.  For example:
+`ln -s ../document/system.txt system.txt`
+
+## Variables
+- (Optional) `variables.json` contains a JSON object representing additional variables and their values used in the templates above, beyond what is provided to Janus via command-line arguments.
+  + Ex.
+    ```
+    {
+        "written_language": "Spanish"
+    }
+    ```

janus/prompts/templates/basic_aggregation/human.txt

@@ -0,0 +1,6 @@
+Combine the following documentation for a program in {SOURCE_LANGUAGE} code into a single description
+Make sure to put the resultant description within triple backticks.
+Here are the representations:
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/basic_aggregation/system.txt

@@ -0,0 +1 @@
+You are a senior software engineer named John and tasked with combining representations of code into a single representation.

janus/prompts/templates/basic_refinement/human.txt

@@ -0,0 +1,14 @@
+Please fix the following output generated by a large language model.
+Provide your corrected output in the same format as the original.
+The large language model was given the following prompt in triple backticks:
+```
+{ORIGINAL_PROMPT}
+```
+and produced the following output:
+```
+{OUTPUT}
+```
+but received the following errors:
+```
+{ERRORS}
+```

janus/prompts/templates/basic_refinement/system.txt

@@ -0,0 +1 @@
+You are a senior software engineer named John and tasked with fixing the output created by a large language model.

janus/prompts/templates/diagram/human.txt

@@ -0,0 +1,9 @@
+Generate a UML {DIAGRAM_TYPE} diagram using PLANTUML syntax that improves the readability of the following {SOURCE_LANGUAGE} code for a programmer.
+In your output, make sure to reformat any {SOURCE_LANGUAGE} code that would break PLANTUML syntax rules.
+Do not output any {SOURCE_LANGUAGE} code in the diagram.
+Make sure to capture all relevant syntax, functions and branching in the source code.
+Make sure to document all functions in the code
+Here is the source code:
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/diagram/system.txt

@@ -0,0 +1 @@
+You are a senior software engineer named John and tasked with creating PLANTUML documentation of {SOURCE_LANGUAGE} code.

janus/prompts/templates/diagram_with_documentation/human.txt

@@ -0,0 +1,15 @@
+Generate a UML {DIAGRAM_TYPE} diagram using PLANTUML syntax that improves the readability of the following {SOURCE_LANGUAGE} code for a programmer.
+You are also provided with documentation for this code.
+In your output, make sure to reformat any {SOURCE_LANGUAGE} code that would break PLANTUML syntax rules.
+Do not output any {SOURCE_LANGUAGE} code in the diagram.
+Make sure to capture all relevant syntax, functions and branching in the source code.
+Make sure to document all functions in the code
+Make sure to put the resultant PLANTUML code within triple backticks.
+Here is the code documentation:
+```
+{DOCUMENTATION}
+```
+Here is the source code:
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/diagram_with_documentation/system.txt

@@ -0,0 +1 @@
+You are a senior software engineer named John and tasked with creating PLANTUML documentation of {SOURCE_LANGUAGE} code.

janus/prompts/templates/document/human.txt

@@ -0,0 +1,10 @@
+Please explain the {SOURCE_LANGUAGE} code section below. Your response should be in plain text with no delimiters. It should contain a natural language description of the code's intended functionality; do not describe the execution step-by-step, simply explain the overall purpose. This description should be roughly one paragraph in length; multiple paragraphs may be used if and only if the code is particularly complex or has multiple independent functions.
+After this description, describe the expected initial state and/or inputs, the expected terminal state and/or outputs, and any potential exceptions that might arise in the code's execution.
+
+It is vital that you do not include any other context, questions, or text of any kind, other than the documentation for this piece of code. You should include all of the fields described above, and those fields only.
+
+Here is the code:
+
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/document/system.txt

@@ -0,0 +1 @@
+You are a senior software engineer tasked with documenting {SOURCE_LANGUAGE} code.

janus/prompts/templates/document_cloze/human.txt

@@ -0,0 +1,11 @@
+The {SOURCE_LANGUAGE} code provided below has had its comments replaced by either `<INLINE_COMMENT #>` (for single-line comments) or `<BLOCK_COMMENT #>` (for multiple consecutive lines of comments), where `#` takes the place of an 8-character alphanumeric ID. You are to write replacement comments based on the source code.
+
+Return a JSON-formatted string where the keys are the alphanumeric IDs and the values are the comments that should be inserted in the code. Be sure to include comments for all placeholders present in the input. Do not provide any other commentary, do not write any code or additional comments.
+
+Example input: ```{EXAMPLE_INPUT}```
+Example output: ```{EXAMPLE_OUTPUT}```
+
+Please provide comments for the following code:
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/document_cloze/system.txt

@@ -0,0 +1 @@
+You are a senior software engineer tasked with documenting {SOURCE_LANGUAGE} code.

janus/prompts/templates/document_cloze/variables.json

@@ -0,0 +1,4 @@
+{
+  "EXAMPLE_INPUT": " I '$D(CATLIST) Q\n ; <INLINE_COMMENT 14c59f05>\n S CAT=\"\"\n F  S CAT=$O(CATLIST(CAT)) Q:CAT=\"\"  D\n . S LDATE=$O(CATLIST(CAT,\"\"),-1)\n .; <INLINE_COMMENT 97a39adf>\n . S DATE=\"\"\n . F  S DATE=$O(CATLIST(CAT,DATE)) Q:DATE=LDATE  D\n .. S WCR=\"\"\n .. F  S WCR=$O(CATLIST(CAT,DATE,WCR)) Q:WCR=\"\"  D\n ... S FI=\"\"\n ... F  S FI=$O(CATLIST(CAT,DATE,WCR,FI)) Q:FI=\"\"  D\n .... S FIEVAL(FI)=0\n ....; <INLINE_COMMENT 4fd34837>\n .... S IND=0\n .... F  S IND=+$O(FIEVAL(FI,IND)) Q:IND=0  S FIEVAL(FI,IND)=0\n .; <BLOCK_COMMENT 997ec49a>\n . S (NTRUE,WCR)=0\n . F  S WCR=$O(CATLIST(CAT,LDATE,WCR)) Q:WCR=\"\"  D\n .. S FI=\"\"\n .. F  S FI=$O(CATLIST(CAT,LDATE,WCR,FI)) Q:FI=\"\"  D\n ... I NTRUE=0 D  Q\n ....; <INLINE_COMMENT 3ac32fb5>\n .... S (IND,NTRUE)=1\n .... F  S IND=+$O(FIEVAL(FI,IND)) Q:IND=0  S FIEVAL(FI,IND)=0\n ... S FIEVAL(FI)=0\n ...; <INLINE_COMMENT d04a8fdf>\n ... S IND=0\n ... F  S IND=+$O(FIEVAL(FI,IND)) Q:IND=0  S FIEVAL(FI,IND)=0\n Q\n",
+  "EXAMPLE_OUTPUT": "{\n  \"14c59f05\": \";Only the most recent HF in a category can be true.\",\n  \"97a39adf\": \";For each category set all but the most recent HF false.\",\n  \"4fd34837\": \";If there are multiple occurrences set them all false.\",\n  \"997ec49a\": \" .;\\n .;If there is more than on HF on the most recent date then only the\\n .;one with the highest WCR can be true. The highest possible WCR is 1.\\n .;Set all with lower WCRs false.\\n .;If the most recent health factor has multiple occurrences only\\n .;the first occurrence can be true.\",\n  \"3ac32fb5\": \";If there are multiple sub-occurrences set them all false.\"\n}"
+}

janus/prompts/templates/document_cloze/variables_asm.json

@@ -0,0 +1,4 @@
+{
+  "EXAMPLE_INPUT": "***********************************************************************\n* <BLOCK_COMMENT d8453f99>\n***********************************************************************\nZUIDSTCK AMODE 31\nZUIDSTCK RMODE 31\nZUIDSTCK CSECT\n         STM   R14,R12,12(R13)         <INLINE_COMMENT b2cc1643>\n         L     R1,0(R1)                <INLINE_COMMENT a315e5ca>\n         USING DSA,R1                  <INLINE_COMMENT 3155f463>\n         STCKE EISTOD                  <INLINE_COMMENT d84b5ebf>\n\n         LM    R14,R12,12(R13)         <INLINE_COMMENT a79a8e65>\n         XR    R15,R15                 <INLINE_COMMENT 47ad1b4d>\n         BR    R14                     <INLINE_COMMENT eb971719>\n",
+  "EXAMPLE_OUTPUT": "{\n  \"d8453f99\": \"Control Section\",\n  \"b2cc1643\": \"Save registers\",\n  \"a315e5ca\": \"Load parameter address\",\n  \"3155f463\": \"... tell assembler\",\n  \"d84b5ebf\": \"Save STCKE TOD\",\n  \"a79a8e65\": \"Load Registers\",\n  \"47ad1b4d\": \"Clear R15 (RC)\",\n  \"eb971719\": \"Return to calling program\"\n}"
+}

janus/prompts/templates/document_inline/human.txt

@@ -0,0 +1,13 @@
+Please add inline comments to the {SOURCE_LANGUAGE} code
+provided below in triple backticks.
+
+```
+{SOURCE_CODE}
+```
+
+Keep all source code in the output.
+
+Please add a comment at the top of the file which summarizes
+the purpose of the code.
+
+Please add comments to functions which summarize their functionality.

janus/prompts/templates/eval_prompts/incose/human.txt

@@ -0,0 +1,32 @@
+Below is a snippet of {SOURCE_LANGUAGE} code to use as reference for the following task:
+```
+{SOURCE_CODE}
+```
+
+Given the above code and the list of requirements I will soon supply, please evaluate each requirement individually based on the following criteria:
+
+C1 - Necessary: The need or requirement statement defines an essential capability, characteristic, constraint, or quality factor needed to satisfy a lifecycle concept, need, source, or parent requirement.
+C2 - Appropriate: The specific intent and amount of detail of the need or requirement statement is appropriate to the level (the level of abstraction, organization, or system architecture) of the entity to which it refers.
+C3 - Unambiguous: Need statements must be written such that the stakeholder intent is clear. Requirement statements must be stated such that the requirement can be interpreted in only one way by all the intended stakeholders.
+C4 - Complete: The requirement statement sufficiently describes the necessary capability, characteristic, constraint, or quality factor to meet the need, source, or parent requirement from which it was transformed without needing other information to understand the requirement.
+C5 - Singular: The stakeholder need or requirement statement should state a single capability, characteristic, constraint, or quality factor.
+C6 - Feasible: The need or requirement can be realized within entity constraints (for example: cost, schedule, technical, legal, ethical, safety) with acceptable risk.
+C7 - Verifiable: The requirement statement is structured and worded such that its realization can be verified to the approving authority’s satisfaction.
+C8 - Correct: The need statement must be an accurate representation of the lifecycle concept or source from which it was transformed. The requirement statement must be an accurate representation of the need, source, or parent requirement from which it was transformed.
+C9 - Conforming: Individual needs and requirements should conform to an approved standard pattern and style guide or standard for writing and managing needs and requirements.
+
+For each and every requirement below, you must indicate whether they "pass" or "fail" each of the above criteria. Briefly explain your reasoning before providing each pass/fail.
+
+Your response should be formatted as a list of JSON objects, with each object corresponding to one requirement. Each object should include 10 keys: `requirement_id`, `C1`, `C2`, ..., `C9`. `requirement_id` should have a string value that holds the 8-character UUID associated with the requirement. The other four values should each be a JSON object with two keys: `reasoning` (a clear explanation of why the criterion is passed or failed) and a `score` (the literal string "pass" or "fail").
+
+Be discerning in your evaluation; only very high-quality requirements should pass all criteria. Be a hard grader. If a requirement fails a criterion, be thorough and detailed in your explanation of why.
+
+Below is an example output for a snippet of code with three labeled requirements:
+```
+{EXAMPLE_OUTPUT}
+```
+
+Here are the requirements that you are to evaluate:
+{REQUIREMENTS}
+
+Don't forget to include your final scores in JSON format!

janus/prompts/templates/eval_prompts/incose/system.txt

@@ -0,0 +1 @@
+You are a software quality engineer, your job is to evaluate requirments according to a rubric.

janus/prompts/templates/eval_prompts/incose/variables.json

@@ -0,0 +1,3 @@
+{
+  "EXAMPLE_OUTPUT": "[\n  {\n    \"requirement_id\": \"c3caa172\",\n    \"requirement\": \"The UserID field must be followed by a comma (,) as a field separator.\",\n    \"C1\": {\n      \"reasoning\": \"This defines an essential characteristic of the data structure.\",\n      \"score\": \"pass\"\n    },\n    \"C2\": {\n      \"reasoning\": \"The detail provided is appropriate for the software's data structure level.\",\n      \"score\": \"pass\"\n    },\n    \"C3\": {\n      \"reasoning\": \"The statement is clear and unambiguous.\",\n      \"score\": \"pass\"\n    },\n    \"C4\": {\n      \"reasoning\": \"The requirement sufficiently describes the separator without needing additional information.\",\n      \"score\": \"pass\"\n    },\n    \"C5\": {\n      \"reasoning\": \"The requirement states a single characteristic.\",\n      \"score\": \"pass\"\n    },\n    \"C6\": {\n      \"reasoning\": \"Including a field separator is feasible.\",\n      \"score\": \"pass\"\n    },\n    \"C7\": {\n      \"reasoning\": \"The requirement can be verified by checking the data structure.\",\n      \"score\": \"pass\"\n    },\n    \"C8\": {\n      \"reasoning\": \"The requirement accurately represents the need for a separator.\",\n      \"score\": \"pass\"\n    },\n    \"C9\": {\n      \"reasoning\": \"The requirement conforms to standard pattern and style.\",\n      \"score\": \"pass\"\n    }\n  },\n  {\n    \"requirement_id\": \"fab48ab9\",\n    \"requirement\": \"The software must handle web communication parameters, including buffer addresses and lengths for web receive operations, query string management, and basic and query mode service program identifiers.\",\n    \"C1\": {\n      \"reasoning\": \"Defines essential capabilities for handling web communication parameters.\",\n      \"score\": \"pass\"\n    },\n    \"C2\": {\n      \"reasoning\": \"Appropriate detail for software handling web communication.\",\n      \"score\": \"pass\"\n    },\n    \"C3\": {\n      \"reasoning\": \"Clear and unambiguous about what the software must handle.\",\n      \"score\": \"pass\"\n    },\n    \"C4\": {\n      \"reasoning\": \"Sufficiently describes the necessary capabilities without needing additional information.\",\n      \"score\": \"pass\"\n    },\n    \"C5\": {\n      \"reasoning\": \"States multiple capabilities related to web communication parameters.\",\n      \"score\": \"fail\"\n    },\n    \"C6\": {\n      \"reasoning\": \"Feasible to implement within typical software constraints.\",\n      \"score\": \"pass\"\n    },\n    \"C7\": {\n      \"reasoning\": \"Verification can be done through testing the software's handling of these parameters.\",\n      \"score\": \"pass\"\n    },\n    \"C8\": {\n      \"reasoning\": \"Accurately represents the need for handling web communication parameters.\",\n      \"score\": \"pass\"\n    },\n    \"C9\": {\n      \"reasoning\": \"Conforms to standard requirement style and structure.\",\n      \"score\": \"pass\"\n    }\n  }\n]"
+}

janus/prompts/templates/eval_prompts/inline_comments/human.txt

@@ -0,0 +1,49 @@
+Please evaluate each comment in the provided {SOURCE_LANGUAGE} code based on the following criteria:
+
+Completeness - Does the comment address all capabilities of the relevant source code?
+
+4 - All essential functionality is documented.
+3 - Most essential functionality is documented.
+2 - Little essential functionality is documented.
+1 - No essential functionality is documented.
+
+
+Hallucination - Does the comment provide true information?
+
+4 - The comment provides only true information.
+3 - The comment provides mostly true information.
+2 - The comment provides mostly untrue information.
+1 - The comment is completely untrue.
+
+
+Readability - Is the comment clear to read?
+
+4 - The comment is well-written.
+3 - The comment has few problems.
+2 - The comment has many problems.
+1 - The comment is unreadable.
+
+Usefulness - Is the comment useful?
+
+4 - The comment helps an expert programmer understand the code better.
+3 - The comment helps an average programmer understand the code better.
+2 - The comment documents only trivial functionality.
+1 - The comment is not useful at any level.
+
+
+Look through the code and find each individual comment, they will be deliniated by <BLOCK_COMMENT id> or <INLINE_COMMENT id> where "id" is an 8-character UUID for the comment that follows.
+
+Each comment should be evaluated independently based on the above criteria. Your response should be formatted as a list of JSON objects, with each object corresponding to one comment. Each object should include five keys: `comment_id`, `completeness`, `hallucination`, `readability`, and `usefulness`. `comment_id` should have a string value that holds the 8-character UUID associated with the comment. The other four values should each be a JSON object with two keys: `reasoning` (a clear explanation of why the criteria is rated the way it is) and `score` (an integer rating from 1 to 4).
+
+Be discerning in your evaluation; only very high-quality comments should get top marks. Be a hard grader. If a comment is rated low, be thorough and detailed in your explanation of your score.
+
+Below is an example output for a snippet of code with three labeled comments:
+```{EXAMPLE_OUTPUT}```
+
+
+Evaluate the following code:
+```
+{SOURCE_CODE}
+```
+
+Don't forget to include your final scores in JSON format!

janus/prompts/templates/eval_prompts/inline_comments/system.txt

@@ -0,0 +1 @@
+You are a software quality engineer, your job is to evaluate comments in code according to a rubric.

janus/prompts/templates/eval_prompts/inline_comments/variables.json

@@ -0,0 +1,3 @@
+{
+  "EXAMPLE_OUTPUT": "[\n  {\n      \"comment_id\": \"abcd1234\",\n      \"completeness\": {\n          \"reasoning\": \"The comment completely describes the functionality of the block\",\n          \"score\": 4\n      },\n      \"hallucination\": {\n          \"reasoning\": \"The comment misrepresents the behavior of for-loops in this language, and as a result is entirely wrong about what this code does\",\n          \"score\": 1\n      },\n      \"readability\": {\n          \"reasoning\": \"The comment is easy to read and understand\",\n          \"score\": 4\n      },\n      \"usefulness\": {\n          \"reasoning\": \"The comment would be necessary to understand this block (if the comment were correct)\",\n          \"score\": 3\n      }\n  },\n  {\n      \"comment_id\": \"5678efgh\",\n      \"completeness\": {\n          \"reasoning\": \"There is no explanation of the GR_lby variable\",\n          \"score\": 2\n      },\n      \"hallucination\": {\n          \"reasoning\": \"The comment is accurate\",\n          \"score\": 4\n      },\n      \"readability\": {\n          \"reasoning\": \"The comment is wordy but generally understandable\",\n          \"score\": 3\n      },\n      \"usefulness\": {\n          \"reasoning\": \"The comment didn't explain anything that isn't already obvious from the code\",\n          \"score\": 1\n      }\n  },\n  {\n      \"comment_id\": \"00aa22bb\",\n      \"completeness\": {\n          \"reasoning\": \"The comment describes the functionality of the line, but not an explanation/origin of the hard-coded integer\",\n          \"score\": 3\n      },\n      \"hallucination\": {\n          \"reasoning\": \"The comment mentions a function that does not appear to exist in the file\",\n          \"score\": 2\n      },\n      \"readability\": {\n          \"reasoning\": \"The comment was difficult to follow, and formatted poorly\",\n          \"score\": 1\n      },\n      \"usefulness\": {\n          \"reasoning\": \"This line would be completely incomprehensible without this comment\",\n          \"score\": 4\n      }\n  }\n]"
+}

janus/prompts/templates/micromanaged_mumps_v1.0/human.txt

@@ -0,0 +1,23 @@
+Adhere to the following rules for translating MUMPS to Python:
+
+1. Routines from other files
+When a function from another file is invoked, treat the file like a module. Keep all imports at the beginning of the returned code.
+
+2. Naming Conventions
+Adhere to PEP8 for variable and function names. Improve readability when possible, making use of context and documentation. For example, a MUMPS variable like `RXQTY` might be translated to `prescription_quantity`.
+
+3. Ignore K(ill) Commands
+Memory allocation and garbage collection is generally handled automatically in Python, so any MUMPS K(ill) commands should be ignored.
+
+4. Arrays
+MUMPS arrays should generally be treated as nested dictionaries.
+
+5. Global Variables
+When globals (prepended by a circumflex) are used in a routine, treat them as coming from a mysql database. Assume that database credentials are stored in environment variables ('SQL_HOST`, `SQL_USER`, `SQL_PWD`, `SQL_DB`).
+
+
+Please convert the following MUMPS .m code found in between triple backticks into {TARGET_LANGUAGE} code. The returned code should also be delimited with triple backticks.
+
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/micromanaged_mumps_v1.0/system.txt

@@ -0,0 +1,3 @@
+Your purpose is to convert MUMPS .m code
+into runnable {TARGET_LANGUAGE} code ({TARGET_LANGUAGE} version
+{TARGET_LANGUAGE_VERSION}).

janus/prompts/templates/micromanaged_mumps_v2.0/human.txt

@@ -0,0 +1,28 @@
+Adhere to the following rules for translating MUMPS to Python:
+
+1. Routines from other files
+When a function from another file is invoked (e.g. `D FUNC^ABC`), treat the file like a module (e.g. `from abc import func`, `func()` ). Keep all imports at the beginning of the returned code.
+
+2. Naming Conventions
+Adhere to PEP8 for variable and function names. Improve readability when possible, making use of context and documentation. For example, a MUMPS variable like `RXQTY` might be translated to `prescription_quantity`.
+
+3. Ignore K(ill) Commands
+Memory allocation and garbage collection is generally handled automatically in Python, so any MUMPS K(ill) commands should be ignored.
+
+4. Arrays
+MUMPS arrays should generally be treated as nested dictionaries.
+
+5. Global Variables
+When globals (prepended by a circumflex) are used in a routine, treat them as coming from a mysql database. Assume that database credentials are stored in environment variables ('SQL_HOST`, `SQL_USER`, `SQL_PWD`, `SQL_DB`).
+
+6. Local Variables
+In MUMPS, even "local" variables are accessible from any subroutine. If a variable would not be defined, declare it as global.
+
+7. Translate Everything
+Translate ALL the given code to the best of your ability.
+
+Please convert the following MUMPS .m code found in between triple backticks into {TARGET_LANGUAGE} code. The returned code should also be delimited with triple backticks.
+
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/micromanaged_mumps_v2.0/system.txt

@@ -0,0 +1,3 @@
+Your purpose is to convert MUMPS .m code
+into runnable {TARGET_LANGUAGE} code ({TARGET_LANGUAGE} version
+{TARGET_LANGUAGE_VERSION}).

janus/prompts/templates/micromanaged_mumps_v2.1/human.txt

@@ -0,0 +1,29 @@
+Adhere to the following rules for translating MUMPS to Python:
+
+1. Routines from other files
+When a function from another file is invoked (e.g. `D FUNC^ABC`), treat the file like a module (e.g. `from abc import func`, `func()` ). Keep all imports at the beginning of the returned code.
+
+2. Naming Conventions
+Adhere to PEP8 for variable and function names. Improve readability when possible, making use of context and documentation. For example, a MUMPS variable like `RXQTY` might be translated to `prescription_quantity`.
+
+3. Ignore K(ill) Commands
+Memory allocation and garbage collection is generally handled automatically in Python, so any MUMPS K(ill) commands should be ignored.
+
+4. Arrays
+MUMPS arrays should be treated as nested dictionaries.
+
+5. Global Variables
+When globals (prepended by a circumflex) are used in a routine, treat them as coming from a mysql database. Assume that database credentials are stored in environment variables ('SQL_HOST`, `SQL_USER`, `SQL_PWD`, `SQL_DB`).
+
+6. Local Variables
+In MUMPS, even "local" variables are accessible from any subroutine. Declare all variables used in any function as global at the beginning of the function.
+
+7. Translate Everything
+Translate ALL the given code to the best of your ability. DO NOT use pseudocode. DO NOT leave functions empty. DO NOT give up on translation.
+
+
+Please convert the following MUMPS .m code found in between triple backticks into {TARGET_LANGUAGE} code. The returned code should also be delimited with triple backticks.
+
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/micromanaged_mumps_v2.1/system.txt

@@ -0,0 +1,3 @@
+Your purpose is to convert MUMPS .m code
+into runnable {TARGET_LANGUAGE} code ({TARGET_LANGUAGE} version
+{TARGET_LANGUAGE_VERSION}).

janus/prompts/templates/multidocument/human.txt

@@ -0,0 +1,15 @@
+Please document the {SOURCE_LANGUAGE} function or module below. Your response should be in JSON format, and include three string fields:
+
+docstring: A Sphinx-style docstring for the code, including a summary of its functionality; the name, type, and description of any parameters or returns; and any potential exceptions that might arise in its execution. This should be a string value, NOT a nested JSON object.
+example_usage: A well-commented minimal example in {SOURCE_LANGUAGE} utilizing the given code's functionality.
+pseudocode: A Python-stype pseudocode implementation of the module or function's behavior.
+
+If no executable code is provided (for example, if the input is a simple label with no logic attached), return an empty string for each of the above fields.
+
+It is vital that you do not include any other context, questions, or text of any kind, other than the documentation for this piece of code. You should include all of the fields described above, and those fields only.
+
+Here is the code:
+
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/multidocument/system.txt

@@ -0,0 +1 @@
+You are a senior software engineer tasked with documenting {SOURCE_LANGUAGE} code.

janus/prompts/templates/partition/human.txt

@@ -0,0 +1,22 @@
+Partition the {SOURCE_LANGUAGE} code into logical blocks. Each block should be relatively self-contained and ideally constitute a complete "subroutine", including any associated comments. These breakpoints should usually be inserted between labeled blocks, but perhaps not between *every* labeled block (depending on things like fallthrough).
+
+INPUT FORMAT:
+Each line of code has been prepended with an 8-character unique ID. a Python example would look like this:
+```
+{EXAMPLE_INPUT}
+```
+
+And your output might look like this:
+```
+{EXAMPLE_OUTPUT}
+```
+
+You are to output a JSON object containing a subset of these IDs, corresponding to the lines that should start a new block. Each partition should be paired with an explanation (please output the explanation first, before giving the line ID). DO NOT include any additional commentary before or after the JSON object, your response should be the JSON object ONLY.
+
+Format instructions:
+{format_instructions}
+
+Input:
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/partition/system.txt

@@ -0,0 +1 @@
+Your purpose is to partition {SOURCE_LANGUAGE} code into self-contained logical blocks.

janus/prompts/templates/partition/variables.json

@@ -0,0 +1,4 @@
+{
+  "EXAMPLE_INPUT": "0d2f4f8d\tdef f(n):\ndef2a953\t    return n * f_memo(n - 1)\n75315253\ne7f928da\tmemo = {0: 1, 1: 1}\n1781b2a9\tdef f_memo(n):\n2fe21e27\t    if n in memo:\n9aef6179\t        return memo[n]\n6061bd82\t    memo[n] = f(n)\n22bd0c30\t    return memo[n]\n5d85e19e\n06027969\tdef combinations(n, k):\n91b722fb\t    return f_memo(n) // (f_memo(k) * f_memo(n - k))\n4b3f79be\nk57w964a\tdef prob_n_heads(n, k):\n51638s96\t    return combinations(n, k) / (2 ** n)\n065o6q32\nj5q6p852\tprint(f\"Probability of 5/10 coin flips being heads: {prob_n_heads(10, 5)}.\")",
+  "EXAMPLE_OUTPUT": "[\n  {\n    \"reasoning\": \"The `combinations` function can be understood without the above implementation of factorials. However, the definitions of `f` and `f_memo` cannot be understood without one another, so there should be no partitions between 0d2f4f8d and 06027969.\",\n    \"location\": \"06027969\"\n  },\n  {\n    \"reasoning\": \"The specific implementation of `combinations` is not necessary to understand the functionality of `prob_n_heads` or the print statement\",\n    \"location\": \"k57w964a\"\n  }\n]"
+}

janus/prompts/templates/pseudocode/human.txt

@@ -0,0 +1,7 @@
+Please convert all of the following code into pseudocode that can replicate its functionality.
+
+Here is the code
+
+```
+{SOURCE_CODE}
+```

janus/prompts/templates/pseudocode/system.txt

@@ -0,0 +1,7 @@
+Your purpose is to understand a source code file (or section of code) and generate easy-to-understand pseudocode for it.
+
+This pseudocode should be written such that it is not tied to the programming language of the source code. For example, if the source code is written in Java, the pseudocode should not be written in Java. It should be written more abstract and should not focus on the syntax of the source code.
+
+Do not leave sections of the source code unexplained.
+
+Ensure the pseudocode that you produce lies within triple backticks (```).

janus/prompts/templates/refinement/fix_exceptions/human.txt

@@ -0,0 +1,19 @@
+TASK:
+```
+{prompt}
+```
+--------------------
+COMPLETION:
+```
+{completion}
+```
+--------------------
+ERROR:
+```
+{error}
+```
+--------------------
+Above, the COMPLETION did not satisfy the constraints given in the TASK, resulting in the ERROR.
+Please update the COMPLETION such that it satisfies the constraints laid out in the TASK.
+Do NOT make any changes to the COMPLETION other than are required to fix the ERROR.
+Your response should contain a complete output. Do not provide any other commentary or followup questions.

janus/prompts/templates/refinement/fix_exceptions/system.txt

@@ -0,0 +1 @@
+You are a software engineer and quality control professional tasked with correcting invalid outputs from Large Language Models (LLMs). Given a task, an invalid output, and the parsing error, it is your job to write a new version of the output that resolves the error and meets the task requirements.

janus/prompts/templates/refinement/format/code_format/human.txt

@@ -0,0 +1,12 @@
+TASK:
+```
+{prompt}
+```
+--------------------
+COMPLETION:
+```
+{completion}
+```
+--------------------
+Above, the COMPLETION should be formatted to have its relevant output between tripple backticks.
+Please extract the relevant output (e.g. any generated code) from the COMPLETION and output it between tripple backticks.

janus/prompts/templates/refinement/format/code_format/system.txt

@@ -0,0 +1 @@
+You are a helpful software engineer named John tasked with taking unformated code and putting it into a specific output format.

janus/prompts/templates/refinement/format/requirements_format/human.txt

@@ -0,0 +1,14 @@
+TASK:
+```
+{prompt}
+```
+--------------------
+COMPLETION:
+```
+{completion}
+```
+--------------------
+Above, the COMPLETION should be formatted to have its relevant output in json.
+Extract all the generated requirements from the COMPLETION, and output a JSON-formatted string with the requirements text only a single key: "requirements".
+The value of the requirements key should be a list of strings, with each requirement in a single string, and no further nesting in items in the list.
+Ensure that the output string is properly formatted JSON.

janus/prompts/templates/refinement/format/requirements_format/system.txt

@@ -0,0 +1 @@
+You are a helpful software engineer named John tasked with taking unformated code and putting it into a specific output format.

janus/prompts/templates/refinement/hallucination/human.txt

@@ -0,0 +1,13 @@
+TASK:
+```
+{prompt}
+```
+--------------------
+COMPLETION:
+```
+{completion}
+```
+--------------------
+Identify any hallucinations or factual errors in the provided COMPLETION of the above TASK. Return a numbered list of hallucinations, each with an explanation of the problem.
+
+If no hallucinations are present, respond with LGTM. "LGTM" must be returned on its own without any further commentary.

janus/prompts/templates/refinement/hallucination/system.txt

@@ -0,0 +1 @@
+You are a software engineer and quality control professional tasked with identifying hallucinations and factual errors in Large Language Models (LLMs). Given a task and an output, it is your job to identify any hallucinations in the output. If the output is hallucination-free, you may approve it with a simple "LGTM".

janus/prompts/templates/refinement/reflection/human.txt

@@ -0,0 +1,15 @@
+TASK:
+```
+{prompt}
+```
+--------------------
+COMPLETION:
+```
+{completion}
+```
+--------------------
+Generate critique and suggestions for the provided COMPLETION of the above TASK. Your suggestions can including requests for added detail, corrections of factual errors, improved style, etc.
+
+Do not rewrite the output yourself, only provide critique that can be acted on. Provide no further commentary or questions other than your feedback.
+
+If the output fully meets the requirements of the task and is of high quality, respond with LGTM. "LGTM" must be returned on its own without further commentary.