Skip to content
TrustedSkillsbeta
Back to all skills

Git Pushing

Listed
sickn33·vlatest·backend·MIT

Automates committing and pushing code changes to specified Git repositories, streamlining development workflows.

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 sickn33/agentic-awesome-skills --skill git-pushing -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

sickn33

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

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

Commit
5a4cdd9df8
Manifest
skills/git-pushing/SKILL.md
Scanned
0 files
Copies in repo
3 — all of them scanned
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

The git-pushing skill enables an AI agent to execute Git commands related to pushing changes from a local repository to a remote one. It allows for seamless integration with version control systems, ensuring that code modifications are synchronized with remote repositories like GitHub or GitLab.

When to use it

  • You need to push committed changes to a remote repository after making updates locally.
  • Automating deployment workflows where code must be pushed as part of a CI/CD pipeline.
  • Collaborating on projects and sharing your work with team members via version control.

Key capabilities

  • Execute git push commands to send local commits to a remote server.
  • Handle authentication by managing Git credentials or SSH keys when required.
  • Support for specifying branches, tags, or custom remotes during the push operation.

Example prompts

  • "Push my latest changes to the 'main' branch on GitHub."
  • "Commit and push all uncommitted files to the remote repository."
  • "Push the 'feature/new-ui' branch to the origin server."

Tips & gotchas

  • Ensure that your local Git configuration (e.g., username, email) is set up correctly before pushing.
  • If using SSH, make sure your public key is added to the remote service for secure access.