Automatically create professional git commits after completing agent tasks with semantic commit messages.
Automatically creates semantic git commits after agent tasks using `./orchestra/mcp-servers/auto-commit.sh <prefix> <reason> <action>`. Triggered after significant sub-tasks, quality gates, or handoffs to maintain version control with traceable, professional commit messages.
/plugin marketplace add tstomtimes/orchestra/plugin install orchestra@orchestra-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Automatically create professional git commits after completing agent tasks with semantic commit messages.
Call the auto-commit script with:
./orchestra/mcp-servers/auto-commit.sh <prefix> <reason> <action> [agent_name]
prefix (required): Semantic commit type
feat - New featurefix - Bug fixdocs - Documentation changesstyle - Code formattingrefactor - Code refactoringperf - Performance improvementtest - Test additions/updateschore - Build/tool changesreason (required): Why this change was made
action (required): What was done
agent_name (optional): Agent making the commit
Eden (QA Agent) - After running tests:
# English
./orchestra/mcp-servers/auto-commit.sh \
"test" \
"to ensure code quality" \
"Add comprehensive unit tests for API endpoints" \
"Eden"
# Result: test: Add comprehensive unit tests for API endpoints (to ensure code quality)
# Japanese
./orchestra/mcp-servers/auto-commit.sh \
"test" \
"コード品質を確保するため" \
"APIエンドポイント用の包括的な単体テストを追加" \
"Eden"
# Result: test: APIエンドポイント用の包括的な単体テストを追加 (コード品質を確保するため)
Iris (Security Agent) - After security scan:
./orchestra/mcp-servers/auto-commit.sh \
"chore" \
"to validate deployment security" \
"Run TruffleHog and Grype security scans" \
"Iris"
# Result: chore: Run TruffleHog and Grype security scans (to validate deployment security)
Blake (Release Manager) - After release preparation:
./orchestra/mcp-servers/auto-commit.sh \
"chore" \
"to prepare for production release" \
"Update changelog and version tags for v2.0.0" \
"Blake"
# Result: chore: Update changelog and version tags for v2.0.0 (to prepare for production release)
Mina (Integration Specialist) - After API integration:
./orchestra/mcp-servers/auto-commit.sh \
"feat" \
"to enhance user experience" \
"Implement responsive navigation component" \
"Mina"
# Result: feat: Implement responsive navigation component (to enhance user experience)
Theo (DevOps) - After deployment:
./orchestra/mcp-servers/auto-commit.sh \
"chore" \
"to track deployment state" \
"Update production deployment configuration" \
"Theo"
# Result: chore: Update production deployment configuration (to track deployment state)
Set in .env:
# Enable/disable auto-commits
AUTO_COMMIT_ENABLED=true
# Commit message language
COMMIT_LANGUAGE=en # or 'ja' for Japanese
Format (both languages):
prefix: <action> (<reason>)
Co-Authored-By: <Agent> <noreply@orchestra>
English example:
feat: Add voice notification feature (to support agent announcements)
Co-Authored-By: Eden <noreply@orchestra>
Japanese example:
feat: 音声通知機能を追加 (エージェントのアナウンスをサポートするため)
Co-Authored-By: Eden <noreply@orchestra>
Auto-commit is integrated into all hook stages:
before_task.sh → Main Claude Code commits task planning analysisbefore_pr.sh → Eden commits QA validation resultsbefore_merge.sh → Eden commits integration test resultsbefore_deploy.sh → Iris commits security validationafter_deploy.sh → Theo commits deployment verificationNo changes to commit:
ℹ️ No changes to commit.
→ Normal behavior, script exits gracefully
Not a git repository:
⚠️ Not a git repository. Skipping auto-commit.
→ Script only works in git repositories
Invalid prefix:
❌ Invalid prefix: xyz
Valid prefixes: feat fix docs style refactor perf test chore
→ Use one of the valid semantic prefixes
Auto-commit disabled:
Script exits silently when AUTO_COMMIT_ENABLED=false
Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.