Skip to content
TrustedSkillsbeta
Back to all skills

Git Commit Workflow

Checked
laurigates·vlatest·backend·MIT

Automates Git commit creation, including message generation and staging based on provided code changes and descriptions.

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 laurigates/claude-plugins --skill git-commit-workflow -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

laurigates

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 laurigates/claude-plugins at 45d1d7dcf6.

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

Commit
45d1d7dcf6
Manifest
git-plugin/skills/git-commit-workflow/SKILL.md
Scanned
3 files, 664 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 creation, guiding you through best practices for commit messages and staging. It enforces conventional commits (e.g., feat(scope): description) to ensure clarity and automation-friendliness. The skill also supports explicit staging workflows where files are staged individually, promoting visibility and control over changes being committed.

When to use it

  • When you need help crafting clear and standardized commit messages.
  • To ensure consistent adherence to conventional commits for project consistency.
  • For projects requiring detailed tracking of code changes through well-structured commits.
  • Before committing, to gather context like staged files, diff stats, and related open GitHub issues.

Key capabilities

  • Conventional Commits: Enforces a standardized commit format (type(scope): description).
  • Explicit Staging: Promotes staging individual files for clear visibility.
  • Logical Grouping: Encourages grouping related changes into focused commits.
  • Commit Message Best Practices: Provides guidance on writing concise, factual, and imperative commit messages with issue references.
  • Pre-commit Context Gathering: Offers a script to gather context (status, staged files, diff stats, recent log) before committing, optionally including open GitHub issues for auto-linking.

Example prompts

  • "Generate a conventional commit message for this feature."
  • "Show me the best practices for writing a bug fix commit message."
  • "Run the pre-commit context gathering script with issue matching."

Tips & gotchas

  • This skill primarily focuses on commits to the main branch, and pushes to remote feature branches for pull requests. See the git-branch-pr-workflow skill for more information about that pattern.
  • For advanced commit message formatting like co-authored-by lines or BREAKING CHANGE notes, refer to the git-commit-trailers skill.
  • The pre-commit context gathering script requires the CLAUDE_PLUGIN_ROOT environment variable to be set.