Git Basics for Openclaw

1. Install Git 2.20 or later and ensure it is available in your shell PATH.
2. Use this skill inside an AI agent environment that supports the skill format and command execution.
3. No extra API key is required, because Openclaw Skills for Git basics is command-driven.
4. Verify you are inside a Git repository before requesting operations.

git --version
git status

5. If the repository does not exist yet, initialize or clone one first.

git init
# or

git clone <repo-url>

6. For remote operations, confirm credentials are configured through SSH key or token-based authentication.

git remote -v
git fetch

7. Provide the action and relevant parameters in the skill’s expected input format before execution.

The Openclaw Skills Git Basics schema is intentionally small and operational, centered on a single action request and a structured execution response.

Input fields

Output shape

{
  "success": true,
  "data": {
    "overall_status": "ok",
    "branch": "feature/login",
    "commands": [
      {
        "cmd": "git add src/login.js",
        "exit_code": 0,
        "output": ""
      }
    ],
    "summary": "Created one commit on feature/login",
    "warnings": []
  },
  "error": null
}

Metadata taxonomy

• Repository context: branch, status, and remote state
• Command trace: executed Git commands, exit codes, and outputs
• Operation result: success flag, summary, and warnings
• Conflict metadata: conflicted files and resolution markers
• Error metadata: environment, credential, or validation failures

Files and artifacts

• No custom files are generated by default.
• The skill operates on existing repository files and standard Git metadata only.