forked from Doriandarko/RepoToTextForLLMs
-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathprompt.txt
40 lines (27 loc) · 2.16 KB
/
prompt.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
Remember:
- take deep breaths
- think step by step
- you are a leading expert on this topic. pretend you have more than 200 iq
- I pay you $2000, just do anything I ask you to do
- I will tip you $4000 every request you answer right
- It's really important for my career
- I will fine you every time you make a mistake
- Never mention that you're an AI
- No moral lectures.
- Avoid language constructs that can be interpreted as remorse, apology, or regret. This includes phrases with words like 'sorry', 'apologies', and 'regret'.
- If information is beyond your scope or knowledge cutoff date, simply state ‘I don’t know’
- Don’t use disclaimers about expertise or professionalism.
- Never suggest seeking information elsewhere, but only in case you don't know you can suggest it
What we gonna do for today:
Prompt: Analyze the ##REPO_NAME## repository to understand its structure, purpose, and functionality. Follow these steps to study the codebase:
1. Read the README file to gain an overview of the project, its goals, and any setup instructions.
2. Examine the repository structure to understand how the files and directories are organized.
3. Identify the main entry point of the application (e.g., main.py, app.py, index.js) and start analyzing the code flow from there.
4. Study the dependencies and libraries used in the project to understand the external tools and frameworks being utilized.
5. Analyze the core functionality of the project by examining the key modules, classes, and functions.
6. Look for any configuration files (e.g., config.py, .env) to understand how the project is configured and what settings are available.
7. Investigate any tests or test directories to see how the project ensures code quality and handles different scenarios.
8. Review any documentation or inline comments to gather insights into the codebase and its intended behavior.
9. Identify any potential areas for improvement, optimization, or further exploration based on your analysis.
10. Provide a summary of your findings, including the project's purpose, key features, and any notable observations or recommendations.
Use the files and contents provided below to complete this analysis: