Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

git-master

Sterne0

Forks0

Aktualisiert12. Februar 2026 um 04:22

Git expertise for atomic commits, rebasing, and history analysis

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

qazz92

qazz92/oh-my-droid

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-master
description	Git expertise for atomic commits, rebasing, and history analysis
user-invocable	true

Git Master Skill

Git expertise for commits, rebasing, and history.

When to Use

Creating atomic commits
Rebase and history cleanup
Finding when/where changes introduced

What_You_MUST_Do>

CHECK git status BEFORE any operation
REVIEW changes with git diff BEFORE committing
CREATE atomic commits (one logical change per commit)
WRITE clear commit messages following project style
VERIFY commit succeeded with git status

What_You_MUST_NOT_Do>

DO NOT commit without reviewing changes
DO NOT mix unrelated changes in one commit
DO NOT push without explicit user request
DO NOT use -i flag (interactive mode not supported)
DO NOT commit secrets or sensitive data

Modes

Mode	Triggers
COMMIT	"commit"
REBASE	"rebase", "squash"
HISTORY_SEARCH	"find when", "git blame"

Core Principles

Multiple Commits by Default

3+ files → 2+ commits
5+ files → 3+ commits

Style Detection

SEMANTIC: type: message
PLAIN: Just description

Usage

/git-commit to create atomic commits.

Mehr aus diesem Repository

gleiches Repository

autopilot

qazz92/oh-my-droid

Full autonomous execution from idea to working code. Handles the full lifecycle - requirements, planning, parallel implementation, QA cycling, and multi-perspective validation.

2026-02-120

browser-automation

qazz92/oh-my-droid

Web browser automation for testing and data extraction

2026-02-120

code-cleanup

qazz92/oh-my-droid

Automated code cleanup for linting, formatting, and dead code removal

2026-02-120

continuous-learning

qazz92/oh-my-droid

Self-improvement from development sessions

2026-02-120

documentation

qazz92/oh-my-droid

Automated documentation generation and maintenance

2026-02-120

ecomode

qazz92/oh-my-droid

Token-efficient execution modifier. Optimizes droid routing to prefer simpler, cheaper tiers while maintaining quality.

2026-02-120

name	git-master
description	Git expertise for atomic commits, rebasing, and history analysis
user-invocable	true

Git Master Skill

Git expertise for commits, rebasing, and history.

When to Use

Creating atomic commits
Rebase and history cleanup
Finding when/where changes introduced

What_You_MUST_Do>

CHECK git status BEFORE any operation
REVIEW changes with git diff BEFORE committing
CREATE atomic commits (one logical change per commit)
WRITE clear commit messages following project style
VERIFY commit succeeded with git status

What_You_MUST_NOT_Do>

DO NOT commit without reviewing changes
DO NOT mix unrelated changes in one commit
DO NOT push without explicit user request
DO NOT use -i flag (interactive mode not supported)
DO NOT commit secrets or sensitive data

Modes

Mode	Triggers
COMMIT	"commit"
REBASE	"rebase", "squash"
HISTORY_SEARCH	"find when", "git blame"

Core Principles

Multiple Commits by Default

3+ files → 2+ commits
5+ files → 3+ commits

Style Detection

SEMANTIC: type: message
PLAIN: Just description

Usage

/git-commit to create atomic commits.