원클릭으로 Manus에서 모든 스킬 실행

시작하기

git-workflow

스타1

포크0

업데이트2026년 5월 11일 08:45

Use when making changes that should be committed. Enforces atomic commits, meaningful messages, and clean history.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

voidful

voidful/Aixlarity

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Git Workflow

Core Principle

Each commit should represent one logical change. If you cannot describe the commit in one sentence, it is too large.

Commit Message Format

<type>: <description>

<optional body explaining why, not what>

Types: feat, fix, docs, refactor, test, chore.

Before Committing

Run cargo test. All tests must pass.
Run cargo clippy. No warnings.
Run cargo fmt --check. Code is formatted.
Review the diff: git diff --cached. Every changed line should relate to the commit message.

Atomic Commits

Separate refactoring from feature work. Refactor first, commit, then add the feature.
Separate test additions from implementation. Add the test (it fails), commit. Implement (it passes), commit.
Never mix documentation changes with code changes in the same commit.

Aixlarity-Specific Rules

The --git flag in aixlarity exec auto-commits after the session. Use it only when the task is self-contained.
For multi-step tasks, prefer manual commits between steps.

이 저장소의 다른 Skills

같은 저장소

architecture-review

voidful/Aixlarity

Use when evaluating whether a proposed change fits the existing architecture. Prevents layer violations, dependency cycles, and accidental coupling.

2026-05-111

code-review

voidful/Aixlarity

Use when the user wants a code review instead of implementation. Prioritizes correctness bugs, behavioral regressions, missing tests, and risky assumptions.

2026-05-111

documentation-review

voidful/Aixlarity

Use when reviewing documentation for accuracy, completeness, and alignment with source code. Catches doc-code drift before it confuses readers.

2026-05-111

performance-analysis

voidful/Aixlarity

Use when investigating slow execution, high memory usage, or excessive token consumption. Systematic measurement before optimization.

2026-05-111

refactoring

voidful/Aixlarity

Use when improving code structure without changing behavior. Ensures each refactoring step preserves all existing tests.

2026-05-111

security-audit

voidful/Aixlarity

Use when reviewing code for security vulnerabilities. Covers prompt injection, path traversal, command injection, and agent-specific attack vectors.

2026-05-111

name	git-workflow
description	Use when making changes that should be committed. Enforces atomic commits, meaningful messages, and clean history.
version	1.0.0
author	Aixlarity
license	Apache-2.0
metadata	{"aixlarity":{"tags":["git","workflow","version-control","commits"],"related_skills":["code-review","tdd"]}}

Git Workflow

Core Principle

Each commit should represent one logical change. If you cannot describe the commit in one sentence, it is too large.

Commit Message Format

<type>: <description>

<optional body explaining why, not what>

Types: feat, fix, docs, refactor, test, chore.

Before Committing

Run cargo test. All tests must pass.
Run cargo clippy. No warnings.
Run cargo fmt --check. Code is formatted.
Review the diff: git diff --cached. Every changed line should relate to the commit message.

Atomic Commits

Separate refactoring from feature work. Refactor first, commit, then add the feature.
Separate test additions from implementation. Add the test (it fails), commit. Implement (it passes), commit.
Never mix documentation changes with code changes in the same commit.

Aixlarity-Specific Rules

The --git flag in aixlarity exec auto-commits after the session. Use it only when the task is self-contained.
For multi-step tasks, prefer manual commits between steps.