feat: add option for prompt

[pritom007]

• add option for prompt

[github-actions]

action.yml

action.yml

• [MEDIUM] Security Line 5: Potential security risks due to unsanitized custom prompts (Code Snippet: custom-chunk-prompt and custom-summary-prompt)

src/main.py

src/main.py

• [LOW] Code quality Line 68: Potential issues with custom prompts if not properly validated (Code Snippet: os.getenv('CUSTOM_CHUNK_PROMPT') and os.getenv('CUSTOM_SUMMARY_PROMPT'))
• [LOW] Cross-file interactions Line 68: Potential interactions with other files or services due to new environment variables (Code Snippet: os.getenv('CUSTOM_CHUNK_PROMPT') and os.getenv('CUSTOM_SUMMARY_PROMPT'))
• [LOW] Service boundaries Line 68: Potential impact on service boundaries due to custom prompts (Code Snippet: DEFAULT_CHUNK_PROMPT and DEFAULT_SUMMARY_PROMPT)
• [MEDIUM] Data flow changes Line 68: Potential impact on overall data flow due to new custom prompts (Code Snippet: os.getenv('CUSTOM_CHUNK_PROMPT') and os.getenv('CUSTOM_SUMMARY_PROMPT'))
• [LOW] Error handling Line 68: Potential errors if custom prompts are not properly handled and validated (Code Snippet: os.getenv('CUSTOM_CHUNK_PROMPT') and os.getenv('CUSTOM_SUMMARY_PROMPT'))

[github-actions]

action.yml

action.yml

• [MEDIUM] [Security] Line 5: The custom-chunk-prompt and custom-summary-prompt inputs are not validated or sanitized, which could lead to potential security vulnerabilities if malicious input is provided. (custom-chunk-prompt and custom-summary-prompt inputs)

README.md

README.md

• [LOW] [Code Quality] Line 5: The introduction of custom-chunk-prompt and custom-summary-prompt inputs allows for more flexibility in the code review process, but it also increases the complexity of the configuration. (custom-chunk-prompt and custom-summary-prompt inputs)

src/main.py

src/main.py

• [LOW] [Code Quality] Line 6: The DEFAULT_CHUNK_PROMPT and DEFAULT_SUMMARY_PROMPT variables are defined as large strings, which can make the code harder to read and maintain. Consider breaking them down into smaller, more manageable pieces. (DEFAULT_CHUNK_PROMPT and DEFAULT_SUMMARY_PROMPT variables)
• [MEDIUM] [Cross-File Interactions] Line 125: The chunk_prompt and summary_prompt variables are now set based on environment variables, which could lead to inconsistencies between the configuration and the actual prompts used. Consider adding validation or logging to ensure that the prompts are correctly set. (chunk_prompt and summary_prompt variables)
• [LOW] [Service Boundaries] Line 93: The get_pr_diff function is not directly affected by the changes, but it is still responsible for retrieving the PR diff, which is used in the code review process. Consider adding logging or validation to ensure that the PR diff is correctly retrieved and processed. (get_pr_diff function)
• [LOW] [Data Flow Changes] Line 126: The introduction of custom-chunk-prompt and custom-summary-prompt inputs changes the data flow of the code review process, as the prompts are now configurable. Consider adding logging or validation to ensure that the prompts are correctly used and that the code review process is not affected by the changes. (custom-chunk-prompt and custom-summary-prompt inputs)
• [LOW] [Error Handling] Line 129: The tokenizer variable is set based on the tiktoken library, but there is no error handling in case the library is not available or the encoding is not supported. Consider adding try-except blocks to handle potential errors. (tokenizer variable)