Skip to content
TrustedSkillsbeta
Back to all skills

Git

Checked
dalestudy·vlatest·backend·MIT

Automates Git commands like commit, push, pull, and branch management based on provided instructions.

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 dalestudy/skills --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

dalestudy

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 dalestudy/skills at a11368b0a0.

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

Commit
a11368b0a0
Manifest
skills/git/SKILL.md
Scanned
1 file, 422 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 automates common Git commands, helping you manage your code repositories effectively. It enforces best practices for commit messages using Conventional Commits format and guides users through a GitHub Flow workflow with branching strategies. The skill aims to streamline version control tasks by providing structured guidance and automating repetitive actions.

When to use it

  • When creating new commits and needing to adhere to a consistent commit message format (e.g., feat: add ..., fix: resolve ...).
  • When starting a new Git repository and wanting to establish a standard branching strategy like the one described in GitHub Flow.
  • To ensure code changes are clearly documented with concise, informative commit messages that follow established conventions.
  • For teams adopting or enforcing Conventional Commits for improved release note generation and project understanding.

Key capabilities

  • Conventional Commit Enforcement: Guides users to write commit messages following the <type>: <description> format.
  • Branching Strategy Guidance: Provides a recommended branching strategy based on GitHub Flow (main, feature branches, fix branches, refactor branches).
  • Commit Message Formatting Rules: Offers detailed guidelines for crafting clear and concise commit messages including length limits, tense usage, and capitalization rules.
  • Workflow Examples: Illustrates how to initialize repositories with main as the default branch.

Example prompts

  • "Create a commit message for adding dark mode support."
  • "What is the recommended branching strategy for this project?"
  • "Show me an example of a Conventional Commit message for fixing a bug."
  • “How do I change my repository's default branch to main?”

Tips & gotchas

  • The skill relies on user input and understanding of Git concepts. It doesn’t replace the need for basic Git knowledge.
  • While it guides commit message formatting, it does not automatically validate or enforce these rules; users must follow the guidelines provided.