Skip to content
TrustedSkillsbeta
Back to all skills

Semantic Git

Checked
siviter-xyz·vlatest·backend·MIT

Automates Git commit messages and branching based on code changes' semantic meaning, improving clarity and workflow.

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 siviter-xyz/dot-agent --skill semantic-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

siviter-xyz

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 siviter-xyz/dot-agent at 33762551d4.

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

Commit
33762551d4
Manifest
skills/semantic-git/SKILL.md
Scanned
4 files, 469 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 Git commit messages and branching by leveraging conventional commit formats and atomic commits. It aims to improve clarity and workflow within a Git repository, particularly when used with AI IDEs like Cursor. The skill prefers using zagi (a better git interface for agents) if available but falls back to plain git commands otherwise.

When to use it

  • Committing changes to Git
  • Staging files for commit
  • Creating commit messages
  • Managing atomic commits
  • Before pushing changes

Key capabilities

  • Automates Git commit message formatting using conventional commit types (feat, fix, docs, etc.).
  • Enforces atomic commits (grouping related code and tests together).
  • Prefers zagi for Git operations when installed; falls back to plain git.
  • Provides user confirmation before running any Git commands.
  • Displays the exact Git commands that will be executed.

Example prompts

  • "Commit these changes with a 'feat' type."
  • "Stage and commit this file, using conventional commit format."
  • “Create a commit message for this change.”

Tips & gotchas

  • The skill works best when zagi is installed (either via an alias or binary).
  • Even with zagi available, the skill generates plain Git commands.
  • Always expect user confirmation before committing changes.