Skip to content
TrustedSkillsbeta
Back to all skills

Git Pushing

Checked
davila7·vlatest·backend·MIT

Automatically pushes approved frontend code changes to a specified Git repository branch.

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 davila7/claude-code-templates --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

davila7

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 davila7/claude-code-templates at 79182c51fb.

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

Scanned
2 files, 50 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

git-pushing

What it does

This skill enables AI agents to execute Git push commands, allowing them to commit changes and upload code directly to remote repositories. It streamlines the deployment workflow by automating version control updates without manual intervention.

When to use it

  • Deploying frontend updates after completing a UI component or style change.
  • Syncing local development branches with a central remote repository for team collaboration.
  • Pushing bug fixes or hotfixes immediately after resolving an issue in the codebase.
  • Finalizing a feature branch before merging into the main production line.

Key capabilities

  • Executes git push commands to specified remote URLs.
  • Manages authentication tokens and credentials securely during the upload process.
  • Handles branch specifications (e.g., pushing to main, develop, or custom branches).
  • Supports force-push operations when necessary for overwriting remote history.

Example prompts

  • "Commit my latest CSS changes and push them to the 'staging' branch."
  • "Push the current state of the frontend repository to GitHub using my stored credentials."
  • "Upload the new dashboard component code to the remote origin after a successful build."

Tips & gotchas

Ensure your AI agent has read access to the correct Git remote URL and valid authentication tokens before attempting a push. Always verify the target branch name to avoid accidentally overwriting critical production code.