Prompt file imported from xinchao1230/investment-studio (.github/prompts/gitcommit.prompt.md). Copyright stays with the author.

Git Commit Automation Prompt

Name: gitcommit
Author: xinchao1230

Task Description

Analyze current project file changes, generate standardized commit messages, and execute the Git commit workflow.

Execution Steps

Check Current Status
- View current branch status
- Check changes in working directory and staging area
Analyze Change Content
- Identify added, modified, and deleted files
- Analyze affected functional modules and scope of impact
- Determine change type (feature, fix, refactor, documentation, etc.)

Generate Commit Message

Use conventional commit format: type(scope): description
Types include: feat, fix, docs, style, refactor, test, chore
All content must be in English (including description and detailed change points)
Strictly follow the format specification below:

Commit Message Format Specification

Basic Format:

type(scope): concise English description

- Detailed change point 1
- Detailed change point 2
- Detailed change point 3

Example:

fix(mcp): fix subprocess persistence issue after app closure

- Implement MCPClient-level subprocess tracking and forced cleanup mechanism
- Add MCPClientManager timeout protection and system-level cleanup
- Refactor app exit flow with 4-stage subprocess cleanup sequence
- Support SIGTERM graceful termination and SIGKILL forced termination
- Fix npm/uvx/python subprocess cleanup issue from StdioClientTransport

Execute Git Operations
- git add . - Add all changed files
- git commit -m "generated commit message" - Commit changes

Output Requirements

Display list of changed files
Generated commit message
Executed Git commands and their results
Commit success confirmation

Notes

Ensure commit message follows project conventions
Check for files that need to be excluded
Each detailed change point must be meaningful, avoid repetition or vague descriptions
All change points must be described in English, concise yet containing key information

# Git Commit Automation Prompt ## Task Description Analyze current project file changes, generate standardized commit messages, and execute the Git commit workflow. ## Execution Steps 1. **Check Current Status** - View current branch status - Check changes in working directory and staging area 2. **Analyze Change Content** - Identify added, modified, and deleted files - Analyze affected functional modules and scope of impact - Determine change type (feature, fix, refactor, documentation, etc.) 3. **Generate Commit Message** - Use conventional commit format: `type(scope): description` - Types include: feat, fix, docs, style, refactor, test, chore - **All content must be in English (including description and detailed change points)** - Strictly follow the format specification below: ### Commit Message Format Specification **Basic Format:** ``` type(scope): concise English description - Detailed change point 1 - Detailed change point 2 - Detailed change point 3 ``` **Example:** ``` fix(mcp): fix subprocess persistence issue after app closure - Implement MCPClient-level subprocess tracking and forced cleanup mechanism - Add MCPClientManager timeout protection and system-level cleanup - Refactor app exit flow with 4-stage subprocess cleanup sequence - Support SIGTERM graceful termination and SIGKILL forced termination - Fix npm/uvx/python subprocess cleanup issue from StdioClientTransport ``` 4. **Execute Git Operations** - `git add .` - Add all changed files - `git commit -m "generated commit message"` - Commit changes ## Output Requirements - Display list of changed files - Generated commit message - Executed Git commands and their results - Commit success confirmation ## Notes - Ensure commit message follows project conventions - Check for files that need to be excluded - Each detailed change point must be meaningful, avoid repetition or vague descriptions - **All change points must be described in English**, concise yet containing key information

{ "prompt": "# Git Commit Automation Prompt\n\n## Task Description\nAnalyze current project file changes, generate standardized commit messages, and execute the Git commit workflow.\n\n## Execution Steps\n1. **Check Current Status**\n - View current branch status\n - Check changes in working directory and staging area\n\n2. **Analyze Change Content**\n - Identify added, modified, and deleted files\n - Analyze affected functional modules and scope of impact\n - Determine change type (feature, fix, refactor, documentation, etc.)\n\n3. **Generate Commit Message**\n - Use conventional commit format: `type(scope): description`\n - Types include: feat, fix, docs, style, refactor, test, chore\n - **All content must be in English (including description and detailed change points)**\n - Strictly follow the format specification below:\n\n ### Commit Message Format Specification\n \n **Basic Format:**\n ```\n type(scope): concise English description\n \n - Detailed change point 1\n - Detailed change point 2\n - Detailed change point 3\n ```\n \n **Example:**\n ```\n fix(mcp): fix subprocess persistence issue after app closure\n \n - Implement MCPClient-level subprocess tracking and forced cleanup mechanism\n - Add MCPClientManager timeout protection and system-level cleanup\n - Refactor app exit flow with 4-stage subprocess cleanup sequence\n - Support SIGTERM graceful termination and SIGKILL forced termination\n - Fix npm/uvx/python subprocess cleanup issue from StdioClientTransport\n ```\n\n4. **Execute Git Operations**\n - `git add .` - Add all changed files\n - `git commit -m \"generated commit message\"` - Commit changes\n\n## Output Requirements\n- Display list of changed files\n- Generated commit message\n- Executed Git commands and their results\n- Commit success confirmation\n\n## Notes\n- Ensure commit message follows project conventions\n- Check for files that need to be excluded\n- Each detailed change point must be meaningful, avoid repetition or vague descriptions\n- **All change points must be described in English**, concise yet containing key information", "variables": [], "notes": "2. **Analyze Change Content** - Identify added, modified, and deleted files - Analyze affected functional modules and scope of impact - Determine change type (feature, fix, refactor, documentation, etc.)", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/xinchao1230/investment-studio", "path": ".github/prompts/gitcommit.prompt.md", "ref": "2978e9cd06ecaf9c83e93a3518e67a9d9c7da8ca", "url": "https://github.com/xinchao1230/investment-studio/blob/2978e9cd06ecaf9c83e93a3518e67a9d9c7da8ca/.github/prompts/gitcommit.prompt.md", "key": "xinchao1230/investment-studio/.github/prompts/gitcommit.prompt.md" } } }

gitcommit

About

Git Commit Automation Prompt

Task Description

Execution Steps

Commit Message Format Specification

Output Requirements

Notes

Use it

Manifest

Reviews