|
@@ -57,21 +57,12 @@ Automate the Git commit and push process by intelligently analyzing file changes
|
|
|
- src/pages/exam/ContentAreaMedium.tsx
|
|
|
- src/pages/exam/ContentAreaSmall.tsx
|
|
|
`
|
|
|
-5. when analyzing modified files , ignore the dev.ts file unless the user tell to include the file . This is really important.
|
|
|
-6. when use 'git diff' to get diff context for a file , you should use 'git --no-pager diff XXX' to ensure to get whole content , no pager , no need to manually help to get all contents.
|
|
|
-## 3. Present Command List for User Review
|
|
|
|
|
|
-1. Generate the complete list of Git commands to be executed:
|
|
|
|
|
|
- ```
|
|
|
- git add .
|
|
|
- git commit -m "generated commit message with file paths"
|
|
|
- git push
|
|
|
- ```
|
|
|
|
|
|
-2. Display the command list clearly to the user for review and confirmation.
|
|
|
+## 3. Present Command List for User Review
|
|
|
|
|
|
-3. Show the generated commit message prominently so the user can verify its accuracy.
|
|
|
+1. Show the generated commit message prominently so the user can verify its accuracy.
|
|
|
|
|
|
## 4. Interactive Command Execution Confirmation
|
|
|
|
|
@@ -125,7 +116,9 @@ Automate the Git commit and push process by intelligently analyzing file changes
|
|
|
- Ensure commit messages are informative and include file paths for better tracking
|
|
|
- The workflow assumes the current working directory is already a git repository
|
|
|
- Each command execution should be confirmed successful before proceeding to the next step
|
|
|
-
|
|
|
+- when analyzing modified files , ignore the dev.ts file unless the user tell to include the file . This is really important.
|
|
|
+- when use 'git diff' to get diff context for a file , you should use 'git --no-pager diff XXX' to ensure to get whole content , no pager , no need to manually help to get all contents.
|
|
|
+
|
|
|
</detailed_sequence_steps>
|
|
|
|
|
|
</task>
|