Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

git-commit

Sterne441

Forks88

Aktualisiert13. Mai 2026 um 10:10

Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

agulli

agulli/atlas-agents

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	git-commit
description	Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.
license	MIT
compatibility	Requires git
allowed-tools	Bash(git:*)

Process

Run git status to see all changed files. Read the output carefully.
Run git diff --stat to understand the scope of the change.
Group related changes. If the diff contains unrelated changes (e.g., a bug fix AND a new feature), create separate commits. Do not bundle unrelated work.
Stage files intentionally. Use git add <specific-files>, never git add . unless every changed file belongs in the same logical commit.

Write the commit message using Conventional Commits format:

<type>(<scope>): <description>

<body — explain WHY, not WHAT>

<footer — references, breaking changes>

Types: feat, fix, refactor, docs, test, chore, perf, ci

Verify before committing. Run git diff --cached to review exactly what will be committed. Read the staged diff.
Commit. Run git commit -m "..." with the message.

Rationalizations

Excuse	Rebuttal
"I'll just use `git add .` to save time"	Staging everything blindly leads to committing debug files, env vars, and unrelated changes. Stage intentionally.
"The message 'fix stuff' is fine for now"	Every commit message is permanent history. Write it properly the first time.
"I'll squash these later"	You won't. Write clean commits now.

Verification

git diff --cached output was reviewed before committing
Commit message follows Conventional Commits format
No unrelated changes were bundled into a single commit
No .env, __pycache__, or build artifacts were staged

Mehr aus diesem Repository

gleiches Repository

api-design

agulli/atlas-agents

Design or review REST and GraphQL API interfaces. Use when asked to design an API, review endpoint structure, define request/response schemas, or improve API ergonomics.

2026-05-13441

code-review

agulli/atlas-agents

Perform a structured security and quality audit on source code. Use when asked to review code, audit a pull request, check for vulnerabilities, or assess code quality.

2026-05-13441

data-pipeline

agulli/atlas-agents

Design, build, or debug data processing pipelines. Use when asked to process a dataset, transform data, build an ETL pipeline, schedule batch jobs, or fix data quality issues.

2026-05-13441

database-migration

agulli/atlas-agents

Safely run database schema migrations. Use when asked to update database schema, add columns, create tables, run alembic, or apply Django migrations.

2026-05-13441

dependency-audit

agulli/atlas-agents

Audit project dependencies for vulnerabilities, license issues, and bloat. Use when asked to check dependencies, audit packages, find vulnerable libraries, or reduce bundle size.

2026-05-13441

deploy-checklist

agulli/atlas-agents

Execute a structured deployment to staging or production. Use when asked to deploy, ship, release, push to production, or promote to staging.

2026-05-13441

name	git-commit
description	Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.
license	MIT
compatibility	Requires git
allowed-tools	Bash(git:*)

Process

Run git status to see all changed files. Read the output carefully.
Run git diff --stat to understand the scope of the change.
Group related changes. If the diff contains unrelated changes (e.g., a bug fix AND a new feature), create separate commits. Do not bundle unrelated work.
Stage files intentionally. Use git add <specific-files>, never git add . unless every changed file belongs in the same logical commit.

Write the commit message using Conventional Commits format:

<type>(<scope>): <description>

<body — explain WHY, not WHAT>

<footer — references, breaking changes>

Types: feat, fix, refactor, docs, test, chore, perf, ci

Verify before committing. Run git diff --cached to review exactly what will be committed. Read the staged diff.
Commit. Run git commit -m "..." with the message.

Rationalizations

Excuse	Rebuttal
"I'll just use `git add .` to save time"	Staging everything blindly leads to committing debug files, env vars, and unrelated changes. Stage intentionally.
"The message 'fix stuff' is fine for now"	Every commit message is permanent history. Write it properly the first time.
"I'll squash these later"	You won't. Write clean commits now.

Verification

git diff --cached output was reviewed before committing
Commit message follows Conventional Commits format
No unrelated changes were bundled into a single commit
No .env, __pycache__, or build artifacts were staged