update-submitter
Skill87 starsChanged 6 months agoApache-2.0View on GitHub
Analyzes git status, groups related file changes, and generates standardized Conventional Commits. Invoke when the user wants to commit changes, submit updates, or create a PR.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-skill-reviewerSkill
- code-readerSkill
- dir-organizerSkill
- doc-reviewerSkill
- drawio-designerSkill
- editorial-card-designerSkill
- humanizer-zhSkill
- md-link-checkerSkill
- md-summarizerSkill
- md-translatorSkill
- ontologySkill
- openspec-assistantSkill
- pptx-editorSkill
- pptx-readerSkill
- project-analyzerSkill
- reference-organizerSkill
- self-reviewSkill
- tech-outline-plannerSkill
- web-content-downloaderSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
If necessary, execute git diff or git diff --staged to understand the context of the changes.
- Distinctive: line 28
Ensure that unrelated changes are kept in separate commit groups to maintain a clean git history.
- Very specific: line 34
Follow the Conventional Commits specification format: <type>[optional scope]: <description>.
- Very specific: line 35
Use the appropriate type based on the following standards:
- Distinctive: line 51
Wait for the user's explicit confirmation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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/projectDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

