Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit

Checked
fvadicamo·vlatest·backend·MIT

Automates Git commit creation from code changes, incorporating pre-defined templates and descriptions for consistent version control.

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 fvadicamo/dev-agent-skills --skill git-commit -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

fvadicamo

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 fvadicamo/dev-agent-skills at 8e710c57b4.

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

Commit
8e710c57b4
Manifest
plugins/github-workflow/skills/git-commit/SKILL.md
Scanned
2 files, 321 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

The git-commit skill enables AI agents to execute git commit commands directly within a repository, allowing them to save changes with specific messages and options. It streamlines version control workflows by automating the finalization of code modifications without manual CLI interaction.

When to use it

  • Finalizing a series of staged files after an agent has made multiple code edits.
  • Creating commits with conventional commit messages (e.g., feat:, fix:) based on detected changes.
  • Automating deployment pipelines where every successful build requires an immediate version tag.
  • Resolving merge conflicts by committing the resolved state once the agent fixes discrepancies.

Key capabilities

  • Executes standard git commit syntax with custom messages and flags.
  • Supports interactive options like -a (add all) or specific file targeting.
  • Integrates seamlessly into backend development loops for continuous integration.

Example prompts

  • "Commit all staged changes with the message 'fix: resolve null pointer exception in user service'."
  • "Create a commit for the updated configuration files using the message 'chore: update docker-compose settings'."
  • "Stage the modified test files and commit them with the message 'test: add edge case scenarios for login flow'."

Tips & gotchas

Ensure the repository is properly initialized and changes are staged before invoking this skill, as it relies on existing git state. Avoid using this skill in read-only environments or when the working directory contains uncommitted conflicts that require manual resolution first.