Generate semantic git commits after agent sub-task completion.
npx skills add https://github.com/tstomtimes/orchestra --skill auto-commit-tstomtimes
Please help me install this Agent Skill. Skill: auto-commit Source: https://github.com/tstomtimes/orchestra/tree/main/skills/auto-commit Command: npx skills add https://github.com/tstomtimes/orchestra --skill auto-commit-tstomtimes
Automates the generation of professional, semantic git commits after agent tasks complete, eliminating manual write-work and ensuring consistent messages across teams.
Call the auto-commit script with the required parameters to generate a semantic commit for your recent task.
High-intent search queries and answers about installing and using this skill.
You can automate semantic git commits by running a shell script that generates conventional commit messages automatically. This eliminates manual write-work, ensuring consistent messages across multi-agent workflows after sub-task completion.
To keep attribution for agents in version control, use an automation script that supports an optional agent_name parameter. This improves traceability by attributing semantic commits to the specific agent that completed the task.
Yes, the semantic commit automation supports conventional prefixes including feat, fix, docs, style, refactor, perf, test, and chore. This ensures your automated version history adheres to standard semantic versioning practices.
Yes, you need a shell script located at ./orchestra/mcp-servers/auto-commit.sh to automate commits in multi-agent workflows. This script applies versioning when changes are ready after sub-task completion.
sdk451Initialize a Git repository with an initial commit in Bash or PowerShell.
bdsqqqStage modified files, commit with conventional commits, and push to the remote repository.
memorysaverConstruct and manage dynamic multi-agent workflows in Claude Code.
miounet11Generate conventional commit messages from staged Git changes.
