Skip to content
TrustedSkillsbeta
Back to all skills

Git

Checked
epicenterhq·vlatest·backend

Automates Git repository management within Epicenter HQ, streamlining workflows and ensuring code consistency.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add epicenterhq/epicenter --skill git -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

epicenterhq

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned epicenterhq/epicenter at f9441c8f6d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
f9441c8f6d
Manifest
.agents/skills/git/SKILL.md
Scanned
1 file, 122 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to interact with Git repositories, allowing them to manage version control workflows directly. It facilitates cloning repositories, checking status, and executing standard Git commands to track changes in codebases.

When to use it

  • Automating initial setup by cloning a specific repository into the agent's working directory.
  • Verifying the current state of a project by checking for uncommitted or untracked files.
  • Executing version control operations like staging, committing, and pushing updates without manual CLI intervention.

Key capabilities

  • Cloning remote repositories to local environments.
  • Checking repository status and file changes.
  • Running standard Git commands for version management.

Example prompts

  • "Clone the repository located at https://github.com/example/project into the current working directory."
  • "Check the git status of the project to see if there are any uncommitted changes."
  • "Stage all modified files and create a commit with the message 'Fix login bug'."

Tips & gotchas

Ensure the AI agent has write permissions for the target repository before attempting to clone or push changes. This skill relies on standard Git CLI commands, so complex workflows may require additional context about specific branch strategies or remote configurations.