git-delegation

Delegate authenticated Git operations from a credential-less Worker to a central Manager.

5.3k|652|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill git-delegation-agentscope-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-delegation
Source: https://github.com/agentscope-ai/HiClaw/tree/main/manager/agent/worker-skills/git-delegation
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill git-delegation-agentscope-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Workers often need to run authenticated Git operations (clone, fetch, push) but lack direct access to Git credentials, causing failures or unsafe handling of secrets.

Core Features & Use Cases

  • Delegates any git command that needs authentication: Worker sends a git-request: message to the Manager, and the Manager executes the Git operations using credentials the Worker cannot access.
  • Supports full repo lifecycle workflows: cloning, branch creation/switching, staging/committing, pushing, rebasing, merging, and more.
  • Clear request/response contract: returns git-result: on success or git-failed: with error details on failure, enabling a controlled and auditable workflow.

Use case example: A Worker needs to create a feature branch, modify files, commit changes, and push the branch to a remote repository; it delegates clone/checkout/add/commit/push to the Manager while keeping credentials on the Manager side.

Quick Start

Ask your Worker to send a single git-request: to the Manager containing the target workspace and the complete list of Git operations to execute, with intent included in the CONTEXT block.

Frequently Asked Questions about git-delegation

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

FAQPage Schema
How do I run authenticated git operations in a multi-agent workflow when workers lack credentials?

Authenticated git operations can be delegated from a credential-less worker to a centrally managed manager. The worker sends a git-request message with the workspace path and operations list, and the manager executes the git commands using its own credentials.

Can I delegate branch creation, commits, and pushes to a remote repository from a worker agent?

Yes, full repository lifecycle workflows including branch creation, staging, committing, and pushing can be delegated. The worker specifies the clone, checkout, add, commit, and push operations in a single git-request message for the manager to execute.

What is the message contract for delegating git commands between agents?

The git delegation contract uses a git-request message containing the workspace path and explicit operations list. The manager returns a git-result message on success or a git-failed message with error details on failure.

How do I sync my workspace path when delegating git actions to a manager agent?

Workspace paths are synced via MinIO before sending a git-request message. The worker includes this MinIO-synced workspace path in the request so the manager can locate and execute the git operations on the correct files.

What happens if a delegated git operation fails during manager execution?

If a delegated git operation fails, the manager returns a git-failed message containing error details. This allows the worker to handle the failure gracefully and maintain an auditable workflow history for the attempted repository operations.

Does git delegation support rebasing and merging operations for collaborative task execution?

Yes, git delegation supports rebasing, merging, and other git subcommands needed for collaborative task execution. Any authenticated git command required for repository management can be sent in the operations list for the manager to execute as-is.