git

Clone, branch, commit, and push code repositories via the git command line tool.

37|1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/saolalab/clawforce --skill git-saolalab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/saolalab/clawforce/tree/main/marketplace/roles/software-engineer/workspace/skills/git
Command: npx skills add https://github.com/saolalab/clawforce --skill git-saolalab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a standard, reliable way for agents to manage source code changes and collaborate on repositories, removing ambiguity around repository operations and commit provenance.

Core Features & Use Cases

  • Clone or update repositories to obtain the latest codebase for tasks that modify or analyze source files.
  • Create and switch to feature branches, stage changes, commit with configured author identity, and push branches to remote origins.
  • Support creating pull requests for code review workflows and integration with CI/CD pipelines.

Quick Start

Use the git skill to clone a repository, create a feature branch, commit changes with the agent's configured author identity, and push the branch to the remote.

Frequently Asked Questions about git

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

FAQPage Schema
How do I automate git version control actions for cloning and branching code repositories?

Git version control actions automate cloning, branching, committing, and pushing code repositories. Agents can pull the latest codebase, create feature branches, stage edits, and push branches to remote origins for collaboration.

How does an automated agent commit code changes with a specific author identity?

Automated agent committing respects configured commit identity variables like GIT_AUTHOR_NAME and GIT_AUTHOR_EMAIL. This ensures clear commit provenance and tracks code changes accurately during repository collaboration.

Do I need the git command line tool installed in my environment to manage source code?

Yes, managing source code requires the git command line tool to be available in the environment. The skill relies on this dependency to execute version control actions like cloning and pushing.

Can I create a pull request for code review workflows after pushing a feature branch?

Yes, you can create pull requests for code review workflows and integration with CI/CD pipelines. This happens after creating a feature branch, staging edits, committing, and pushing the branch to the remote origin.

What's the best way to sync local source files with a remote repository before analyzing code?

The best way to sync local source files is to clone or update repositories to obtain the latest codebase. This ensures your environment has the current source files before tasks that modify or analyze them.