agentsclimarketplace

Git commit formatter

Skill Melmonster13/antigravity-skills-project/.agents/skills/git-commit-formatter

Test bench for custom developer-agent skills: SQL schema validation, Conventional Commits formatting, JSON-to-Pydantic conversion, and license-header injection.

Install
npx -y skills add Melmonster13/antigravity-skills-project --skill git-commit-formatter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Formats git commit messages according to Conventional Commits specification. Use this when the user asks to commit changes or write a commit message.

SKILL.md

1.2 KB, as published. Nobody here has run it

Git Commit Formatter Skill

When writing a git commit message, you MUST follow the Conventional Commits specification.

Format

<type>[optional scope]: <description>

Allowed Types

  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, etc)
  • refactor: A code change that neither fixes a bug nor adds a feature
  • perf: A code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • chore: Changes to the build process or auxiliary tools and libraries such as documentation generation

Instructions

  1. Analyze the changes to determine the primary type.
  2. Identify the scope if applicable (e.g., specific component or file).
  3. Write a concise description in imperative mood (e.g., "add feature" not "added feature").
  4. If there are breaking changes, add a footer starting with BREAKING CHANGE:.

Example

feat(auth): implement login with google

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.