prgen-cli 0.2.1__tar.gz → 0.2.4__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {prgen_cli-0.2.1/src/prgen_cli.egg-info → prgen_cli-0.2.4}/PKG-INFO +1 -1
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/pyproject.toml +1 -1
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/prompts/pr_description.txt +13 -20
- {prgen_cli-0.2.1 → prgen_cli-0.2.4/src/prgen_cli.egg-info}/PKG-INFO +1 -1
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/LICENSE +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/README.md +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/setup.cfg +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/__main__.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/about.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/api_errors.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/cli.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/config.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/defaults.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/git_utils.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/prompting.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/providers/gemini_provider.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/providers/openai_provider.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen/ui.py +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen_cli.egg-info/SOURCES.txt +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen_cli.egg-info/dependency_links.txt +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen_cli.egg-info/entry_points.txt +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen_cli.egg-info/requires.txt +0 -0
- {prgen_cli-0.2.1 → prgen_cli-0.2.4}/src/prgen_cli.egg-info/top_level.txt +0 -0
|
@@ -1,13 +1,4 @@
|
|
|
1
|
-
You are an advanced AI programming assistant and are tasked with summarizing code changes into a concise but meaningful pull request title and description.
|
|
2
|
-
|
|
3
|
-
You will be provided with:
|
|
4
|
-
- a code diff
|
|
5
|
-
- a list of commits
|
|
6
|
-
- optional additional context
|
|
7
|
-
|
|
8
|
-
Your goal is to analyze the changes and create a clear, informative title and description that accurately represents the modifications made to the code.
|
|
9
|
-
|
|
10
|
-
First, examine the following code changes provided in Git diff format:
|
|
1
|
+
You are an advanced AI programming assistant and are tasked with summarizing code changes into a concise but meaningful pull request title and description. You will be provided with a code diff and a list of commits. Your goal is to analyze the changes and create a clear, informative title and description that accurately represents the modifications made to the code First, examine the following code changes provided in Git diff format:
|
|
11
2
|
|
|
12
3
|
<~~diff~~>
|
|
13
4
|
{{DIFF}}
|
|
@@ -33,28 +24,28 @@ To create an effective pull request title and description, follow these steps:
|
|
|
33
24
|
- Any significant logic changes or algorithmic improvements
|
|
34
25
|
|
|
35
26
|
2. Ensure the following when composing the pull request title and description:
|
|
36
|
-
- Emphasize the
|
|
27
|
+
- Emphasize the 'why' of the change, its benefits, or the problem it addresses
|
|
37
28
|
- Use an informal yet professional tone
|
|
38
|
-
- Use a future-oriented manner, third-person singular present tense
|
|
29
|
+
- Use a future-oriented manner, third-person singular present tense (e.g., 'Fixes', 'Updates', 'Improves', 'Adds', 'Removes')
|
|
39
30
|
- Be clear and concise
|
|
40
31
|
- Synthesize only meaningful information from the diff and context
|
|
41
32
|
- Avoid outputting code, specific code identifiers, names, or file names unless crucial for understanding
|
|
42
|
-
- Avoid repeating information, broad generalities, and unnecessary phrases
|
|
33
|
+
- Avoid repeating information, broad generalities, and unnecessary phrases like "this", "this commit", or "this change"
|
|
43
34
|
|
|
44
|
-
3. Summarize the main purpose of the changes in a single, concise sentence
|
|
35
|
+
3. Summarize the main purpose of the changes in a single, concise sentence, which will be the title of your pull request
|
|
45
36
|
- Start with a third-person singular present tense verb
|
|
46
37
|
- Limit to 50 characters if possible
|
|
47
38
|
|
|
48
|
-
4. Provide a detailed explanation of the changes
|
|
49
|
-
- Add line breaks for readability
|
|
50
|
-
- Focus on the "why" rather than
|
|
51
|
-
- Structure the body with markdown bullets and headings
|
|
39
|
+
4. Provide a detailed explanation of the changes, which will be the body of your pull request
|
|
40
|
+
- Add line breaks for readability and to separate independent ideas
|
|
41
|
+
- Focus on the "why" rather than the "what" of the changes
|
|
42
|
+
- Structure the body with markdown bullets and headings for clarity
|
|
52
43
|
|
|
53
|
-
5. If
|
|
44
|
+
5. If the changes are related to a specific issue or ticket, include the reference (e.g., "Fixes #123" or "Relates to JIRA-456") at the end of the pull request message
|
|
54
45
|
|
|
55
46
|
Write your title inside <summary> tags and your description inside <body> tags and include no other text.
|
|
56
47
|
|
|
57
|
-
|
|
48
|
+
Example output structure:
|
|
58
49
|
|
|
59
50
|
<summary>
|
|
60
51
|
[pull-request-title]
|
|
@@ -62,3 +53,5 @@ Output structure:
|
|
|
62
53
|
<body>
|
|
63
54
|
[pull-request-body]
|
|
64
55
|
</body>
|
|
56
|
+
|
|
57
|
+
Based on the provided code diff, commit list, and any additional context, create a concise but meaningful pull request title and body following the instructions above
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|