Skip to content
TrustedSkillsbeta
Back to all skills

Commits

Listed
itechmeat·vlatest·writing·MIT

This skill automatically commits code changes to your repository after a successful build, streamlining your workflow and ensuring consistent updates.

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 itechmeat/llm-code --skill commits -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

itechmeat

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: www.conventionalcommits.org.

    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.

    Hosts contacted

    www.conventionalcommits.orgundeclared

    What it found

    • skills/commits/assets/validate-commit-msg.sh:49contacts www.conventionalcommits.org
      echo "See: https://www.conventionalcommits.org/" >&2

  • 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 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 itechmeat/llm-code at 7ae8a00524.

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

Commit
7ae8a00524
Manifest
skills/commits/SKILL.md
Scanned
2 files, 365 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 enables AI agents to automatically generate and apply commit messages adhering to a specific conventional commits format. It structures commit messages with a type, optional scope, description, body, and footer, facilitating automated changelog generation and semantic versioning. The skill ensures that commit messages follow predefined rules for consistency and clarity.

When to use it

  • When automating code changes and ensuring consistent commit message formatting.
  • For projects requiring structured commit history for automated release notes or version management.
  • To streamline the development workflow by reducing manual effort in writing commit messages.
  • In teams adopting conventional commits practices.

Key capabilities

  • Conventional Commit Format: Enforces a standardized format: <type>[optional scope]: <description>\n[optional body]\n[optional footer(s)].
  • Type Specification: Supports common types like feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert.
  • Scope Support: Allows for optional scopes to provide context within the commit message (e.g., feat(auth): ...).
  • Breaking Change Indication: Supports indicating breaking changes using either ! before the colon or a BREAKING CHANGE: footer.
  • Footer Support: Enables adding review information and references in the commit footer.

Example prompts

  • "Commit this change with type 'fix' and scope 'parser', describing how it handles empty arrays."
  • "Create a 'feat' commit for the user authentication feature, including a body explaining the request ID implementation."
  • "Revert the previous commit related to the noodle incident."

Tips & gotchas

  • The skill requires adherence to conventional commits specification. Incorrect formatting may result in rejected commits.
  • Breaking changes must be explicitly marked using either ! or BREAKING CHANGE: to ensure proper versioning and documentation.