Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

git-commit-formatter

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

In Manus ausführen

Überblick

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

Installationsbefehl

npx skills add https://github.com/phenobarbital/antigravity-config --skill git-commit-formatter

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um den Skill zu installieren

Quelle

phenobarbital/antigravity-config

Sterne13

Forks0

Aktualisiert21. Februar 2026 um 01:15

SKILL.md

readonly

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

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

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

Example feat(auth): implement login with google

Mehr aus diesem Repository

gleiches Repository

aws-cost-optimization

phenobarbital/antigravity-config

Evaluate AWS costs and generate actionable optimization suggestions. Covers EC2, S3, RDS, Lambda, ECS/EKS, and data transfer. Use when analyzing AWS spending, right-sizing resources, choosing pricing models (RI/Savings Plans/Spot), implementing tagging strategies, setting budget alerts, or auditing infrastructure for cost waste.

2026-02-2113

aws-serverless

phenobarbital/antigravity-config

Specialized skill for building production-ready serverless applications on AWS. Covers Lambda functions, API Gateway, DynamoDB, SQS/SNS event-driven patterns, SAM/CDK deployment, and cold start optimization.

2026-02-2113

code-review

phenobarbital/antigravity-config

Reviews code changes and provides feedback, code style and best practices.

2026-02-2113

data-storytelling

phenobarbital/antigravity-config

Transform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.

2026-02-2113

docstring

phenobarbital/antigravity-config

Document a Python module and its classes using Google style

2026-02-2113

license-header-adder

phenobarbital/antigravity-config

Adds the standard open-source license header to new source files. Use involves creating new code files that require copyright attribution.

2026-02-2113

Quelle

phenobarbital

phenobarbital/antigravity-config

GitHub-Repository öffnen Creator-Repositorys ansehen

Installationsbefehl

Download

In Manus ausführen

Nützlich fürSOC

ComputerprogrammiererInformatik- und Mathematikberufe15-1251L4

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

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

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

Example feat(auth): implement login with google