update-submitter
Update Submitter
This skill automates the process of reviewing local repository changes, grouping related file modifications, and generating standardized commit messages following the Conventional Commits specification.
1. Core Workflow
The workflow outlines the exact steps to collect changes, group them, and generate commits.
1.1 Target Initialization
Accept the target directory and gather the current state of the repository.
- Accept a target directory path from the user. If no path is provided, default to the current project directory.
- Execute
git statusto retrieve the list of modified, added, deleted, and untracked files. - If necessary, execute
git difforgit diff --stagedto understand the context of the changes.
1.2 Change Analysis and Grouping
Analyze the changed files and group them into logical units that belong in the same commit.
- Review the list of changed files.
- Group files based on their relationships (e.g., UI components together, database schemas together, documentation updates together).
- Ensure that unrelated changes are kept in separate commit groups to maintain a clean git history.
1.3 Commit Message Generation
Generate a standardized commit message for each logical group of changes.
- Follow the Conventional Commits specification format:
<type>[optional scope]: <description>. - Use the appropriate
typebased on the following standards:feat: A new feature.fix: A bug fix.docs: Documentation only changes.style: Changes that do not affect the meaning of the code (white-space, formatting, etc.).refactor: A code change that neither fixes a bug nor adds a feature.perf: A code change that improves performance.test: Adding missing tests or correcting existing tests.chore: Changes to the build process or auxiliary tools and libraries.
- Provide a clear and concise
descriptionof the changes.
1.4 Execution and Confirmation
Present the proposed commit plan to the user and execute upon confirmation.
- Output the proposed commit groups and their corresponding commit messages to the user for review.
- Wait for the user's explicit confirmation.
- Once confirmed, execute the appropriate
git add <files>andgit commit -m "<message>"commands for each group.
2. Usage Examples
These examples demonstrate how to invoke and use the skill in the terminal.
# Invoke the update-submitter skill on the current directory
/update-submitter
# Invoke the update-submitter skill on a specific directory
/update-submitter /path/to/project
More from forceinjection/awesome-skills
doc-reviewer
审查技术文档。支持四种独立评审类型:大纲评审(检查目录与结构逻辑)、内容评审(检查文字准确性与代码质量)、资产评审(校验链接与引用合规)、格式评审(校对纯视觉排版与标点)。当用户请求审查或修正 Markdown 文档时使用。
5agent-skill-reviewer
Review Agent Skill directories and SKILL.md files against best practices. Use this skill when the user wants to review, validate, or check an Agent Skill implementation.
5project-analyzer
Generate a comprehensive project documentation (whitepaper) based on deep codebase analysis, covering architecture, modules, testing, and deployment.
4dir-organizer
整理和优化项目目录结构。当用户请求整理目录、分类文件、清理无用文件或重构文件夹结构时调用此技能。
4code-reader
Use when you want to deeply understand an unfamiliar codebase and generate reusable cognitive skills from it, by providing a local path or GitHub URL
4md-summarizer
分析和总结指定的本地 Markdown 文件,并输出结构化的中文总结。当用户请求总结、分析或提取本地 Markdown 文档信息时调用此技能。
4