Skip to content
TrustedSkillsbeta
Back to all skills

Git Sync Checker

Checked
alongor666·vlatest·backend

Checks your local Git repository against remote branches for divergence and potential merge conflicts.

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 alongor666/chexianduoweifenxi --skill git-sync-checker -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

alongor666

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 alongor666/chexianduoweifenxi at fdcb673604.

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

Commit
fdcb673604
Manifest
.claude/skills/git-sync-checker/SKILL.md
Scanned
1 file, 489 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

The git-sync-checker skill verifies the synchronization status of a Git repository. It checks if local changes have been pushed to a remote branch and reports on any discrepancies, ensuring code consistency across environments. This helps prevent accidental data loss or conflicts when collaborating on projects.

When to use it

  • Before deploying: Confirm that all recent commits are present on the target server.
  • During collaborative development: Quickly check if your local changes align with the remote repository.
  • Troubleshooting deployment issues: Verify code consistency between developer machines and production servers.
  • Automated workflows: Integrate into CI/CD pipelines to automatically validate synchronization before builds or releases.

Key capabilities

  • Checks for pushed commits
  • Reports on synchronization status
  • Supports remote branch verification

Example prompts

  • "Check if my local repository is synced with origin main."
  • "Verify that all changes have been pushed to the remote repository."
  • "Is my current branch up-to-date with the upstream?"

Tips & gotchas

The skill requires access to a Git repository and appropriate credentials. Ensure your AI agent has the necessary permissions to interact with the Git server for accurate results.