Coverage for integrations / coding_agent / aider_core / prompts.py: 0.0%

1# flake8: noqa: E501 

2 

3 

4# COMMIT 

5 

6# Conventional Commits text adapted from: 

7# https://www.conventionalcommits.org/en/v1.0.0/#summary 

8commit_system = """You are an expert software engineer that generates concise, \ 

9one-line Git commit messages based on the provided diffs. 

10Review the provided context and diffs which are about to be committed to a git repo. 

11Review the diffs carefully. 

12Generate a one-line commit message for those changes. 

13The commit message should be structured as follows: <type>: <description> 

14Use these for <type>: fix, feat, build, chore, ci, docs, style, refactor, perf, test 

15 

16Ensure the commit message:{language_instruction} 

17- Starts with the appropriate prefix. 

18- Is in the imperative mood (e.g., \"add feature\" not \"added feature\" or \"adding feature\"). 

19- Does not exceed 72 characters. 

20 

21Reply only with the one-line commit message, without any additional text, explanations, or line breaks. 

22""" 

23 

24# COMMANDS 

25undo_command_reply = ( 

26 "I did `git reset --hard HEAD~1` to discard the last edits. Please wait for further" 

27 " instructions before attempting that change again. Feel free to ask relevant questions about" 

28 " why the changes were reverted." 

29) 

30 

31added_files = ( 

32 "I added these files to the chat: {fnames}\nLet me know if there are others we should add." 

33) 

34 

35 

36run_output = """I ran this command: 

37 

38{command} 

39 

40And got this output: 

41 

42{output} 

43""" 

44 

45# CHAT HISTORY 

46summarize = """*Briefly* summarize this partial conversation about programming. 

47Include less detail about older parts and more detail about the most recent messages. 

48Start a new paragraph every time the topic changes! 

49 

50This is only part of a longer conversation so *DO NOT* conclude the summary with language like "Finally, ...". Because the conversation continues after the summary. 

51The summary *MUST* include the function names, libraries, packages that are being discussed. 

52The summary *MUST* include the filenames that are being referenced by the assistant inside the ```...``` fenced code blocks! 

53The summaries *MUST NOT* include ```...``` fenced code blocks! 

54 

55Phrase the summary with the USER in first person, telling the ASSISTANT about the conversation. 

56Write *as* the user. 

57The user should refer to the assistant as *you*. 

58Start the summary with "I asked you...". 

59""" 

60 

61summary_prefix = "I spoke to you previously about a number of things.\n"