spawn-commit

Name: spawn-commit
Availability: InStock
Author: Zeliper

Spawn commit-agent to create TASK-ID-scoped commits after successful builds.

Updated Dec 25, 2025

Search Tags:#automation #git #workflow #commit #TASK-ID #post-build

Ready to run

npx skills add https://github.com/Zeliper/z-coder --skill spawn-commit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spawn-commit
Source: https://github.com/Zeliper/z-coder/tree/main/.claude/skills/spawn-commit
Command: npx skills add https://github.com/Zeliper/z-coder --skill spawn-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the post-build commit step by spawning the commit-agent to create a structured, TASK-ID-scoped commit after a successful build, reducing manual effort and ensuring consistent commit messages.

Core Features & Use Cases

Post-build Commit: Automatically spawn commit-agent only after the builder-agent reports a successful build.
TASK-ID Enforced Messaging: Ensure commits include the TASK-ID for traceability.
Result Summary & Next Steps: Report the commit outcome and proceed to test-case generation when successful.

Quick Start

Trigger the commit process for a completed task, e.g. TASK-001, with Step 2 and a list of changed files. The system will follow the instructions in .claude/agents/commit-agent.md to perform the commit and return a concise result summary.

Frequently Asked Questions about spawn-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate commits after a successful build?▼

Automate post-build commits by spawning commit-agent after the builder-agent reports a completed build. The Skill coordinates commit creation for specified changed files, enforcing TASK-ID inclusion in commit messages and excluding sensitive files.

How can I ensure commits include task tracking information?▼

The Skill enforces TASK-ID-scoped commit messages automatically. Each commit includes a hash and the TASK-ID for traceability, reducing manual effort and maintaining consistent messaging across your CI workflow.

Can I use this in CI workflows to coordinate commits with build completion?▼

Yes. The Skill spawns commit-agent only after successful builds, making it ideal for CI workflows. It reports commit outcomes and prepares for test-case generation, integrating seamlessly into automated pipelines.

What files are excluded when creating automated commits?▼

The Skill automatically excludes sensitive files from commits while including your specified changed files. This prevents accidental commits of credentials, keys, or other protected data.

Do I need to use Bash commands to trigger the commit process?▼

No. The Skill enforces use of the Task tool rather than Bash, ensuring structured, reliable commit creation that integrates with your workflow agent coordination.