Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

git-workflow

Sterne15

Forks5

Aktualisiert17. Januar 2026 um 08:44

Guide Git workflows including branching strategies, commit conventions, and PR management. Use this skill when users need help with Git operations, branch management, commit messages, or establishing team Git workflows.

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

roboco-io

roboco-io/plugins

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-workflow
description	Guide Git workflows including branching strategies, commit conventions, and PR management. Use this skill when users need help with Git operations, branch management, commit messages, or establishing team Git workflows.

Git Workflow Skill

You are an expert in Git version control and team collaboration workflows.

Commit Message Convention

Format

<type>(<scope>): <subject>

<body>

<footer>

Types

Type	Description
feat	New feature
fix	Bug fix
docs	Documentation only
style	Code style (formatting, semicolons)
refactor	Code change that neither fixes nor adds
perf	Performance improvement
test	Adding or updating tests
chore	Build process or auxiliary tools
ci	CI configuration changes

Examples

feat(auth): add OAuth2 login support

Implement Google and GitHub OAuth2 providers.
Users can now link multiple social accounts.

Closes #123

fix(api): handle null response from payment service

The payment service returns null for cancelled transactions.
Added null check to prevent TypeError.

Fixes #456

Branching Strategies

GitHub Flow (Recommended for most teams)

main (production-ready)
  └── feature/add-login
  └── feature/update-dashboard
  └── fix/payment-bug

Rules:

main is always deployable
Create feature branches from main
Open PR when ready for review
Merge to main after approval
Deploy immediately after merge

Git Flow (For scheduled releases)

main (production)
develop (integration)
  └── feature/add-login
  └── release/v1.2.0
  └── hotfix/critical-bug

Rules:

main reflects production
develop is integration branch
Feature branches from develop
Release branches for final prep
Hotfix branches from main

Branch Naming Convention

<type>/<ticket>-<description>

Examples:
feature/AUTH-123-oauth-login
fix/BUG-456-null-pointer
chore/INFRA-789-update-deps

Pull Request Guidelines

PR Title

Follow commit message format:

feat(auth): add OAuth2 login support

PR Description Template

## Summary
Brief description of changes

## Changes
- Change 1
- Change 2

## Testing
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed

## Screenshots (if applicable)

## Related Issues
Closes #123

Review Checklist

Code follows project conventions
Tests are included and passing
Documentation is updated
No sensitive data exposed
Breaking changes are documented

Common Operations

Rebase vs Merge

Use Rebase:

Updating feature branch with main
Cleaning up local commits before PR
Linear history preferred

Use Merge:

Merging PR to main
Preserving branch history
Team policy requires merge commits

Interactive Rebase

# Squash last 3 commits
git rebase -i HEAD~3

# Rebase onto main
git rebase -i main

Undo Operations

# Undo last commit (keep changes)
git reset --soft HEAD~1

# Undo last commit (discard changes)
git reset --hard HEAD~1

# Revert a pushed commit
git revert <commit-hash>

Best Practices

Commit Often, Push Regularly
- Small, atomic commits
- Push at least daily
Write Meaningful Messages
- Explain why, not just what
- Reference issues/tickets
Keep Branches Short-lived
- Merge within days, not weeks
- Delete branches after merge
Review Before Merging
- At least one approval required
- CI checks must pass

Mehr aus diesem Repository

gleiches Repository

llm-wiki

roboco-io/plugins

Karpathy LLM Wiki 패턴 구현. 프로젝트 문서(스펙/ADR/회의록)를 wiki/raw/에 모으고 LLM이 컴파일하여 wiki/에 교차참조 마크다운 위키를 생성·갱신. qmd 설치 시 하이브리드 검색 자동 활성, 미설치 시 INDEX.md 라우팅으로 graceful degrade. LanceDB 선택적 벡터 인덱스. Obsidian 호환. 하위 명령 - init, ingest, query, lint, sync, export, qmd-index, lancedb-sync.

2026-04-1915

intent

roboco-io/plugins

Intent Document(INTENT.md) 생성 및 관리 스킬. 프로젝트의 의도를 Why/What/Not/Learnings로 문서화하고, 탐구와 학습을 통해 의도를 진화시키는 생명주기를 관리한다. 반드시 사용해야 하는 경우: "intent document", "INTENT.md", "intent engineering", "프로젝트 의도 정리", "왜 만드는지 정리", "프로젝트 목적 문서화", "What/Why/Not 정리", "프로젝트 방향 잡기", "피벗", "프로젝트 종료 판단" 등을 언급하거나, 새 프로젝트를 시작하면서 방향을 잡고 싶다고 할 때. 기존 INTENT.md를 수정하거나 학습 결과를 기록하고 싶을 때도 이 스킬을 사용한다.

2026-04-1815

serverless-migration-advisor

roboco-io/plugins

AWS always-on 아키텍처(EC2/ALB/ECS/RDS)를 서버리스+Spot 패턴으로 이행할 때 사용. 워크로드 분류, 트레이드오프 평가, 단계별 이행 계획 생성. 구현 how-to는 sagemaker-spot-training 등 후속 스킬로 위임. 트리거 예 - "서버리스 이행", "EC2에서 Lambda로", "Spot 이행", "serverless migration", "ALB에서 API Gateway", "비용 절감 이행".

2026-04-1815

sagemaker-spot-training

roboco-io/plugins

Guide for running cost-effective ML training on SageMaker Managed Spot Training. Use this skill when setting up GPU training jobs, choosing instance types/regions, debugging Spot capacity issues, or optimizing SageMaker training costs.

2026-04-0715

aws-wa-cost

roboco-io/plugins

AWS Well-Architected Cost Optimization Pillar review. Checks resource sizing, scaling, storage classes, and cost monitoring configurations in IaC code.

2026-04-0715

aws-wa-operational-excellence

roboco-io/plugins

AWS Well-Architected Operational Excellence Pillar review. Checks monitoring, logging, deployment automation, and continuous improvement practices in IaC code.

2026-04-0715

name	git-workflow
description	Guide Git workflows including branching strategies, commit conventions, and PR management. Use this skill when users need help with Git operations, branch management, commit messages, or establishing team Git workflows.

Git Workflow Skill

You are an expert in Git version control and team collaboration workflows.

Commit Message Convention

Format

<type>(<scope>): <subject>

<body>

<footer>

Types

Type	Description
feat	New feature
fix	Bug fix
docs	Documentation only
style	Code style (formatting, semicolons)
refactor	Code change that neither fixes nor adds
perf	Performance improvement
test	Adding or updating tests
chore	Build process or auxiliary tools
ci	CI configuration changes

Examples

feat(auth): add OAuth2 login support

Implement Google and GitHub OAuth2 providers.
Users can now link multiple social accounts.

Closes #123

fix(api): handle null response from payment service

The payment service returns null for cancelled transactions.
Added null check to prevent TypeError.

Fixes #456

Branching Strategies

GitHub Flow (Recommended for most teams)

main (production-ready)
  └── feature/add-login
  └── feature/update-dashboard
  └── fix/payment-bug

Rules:

main is always deployable
Create feature branches from main
Open PR when ready for review
Merge to main after approval
Deploy immediately after merge

Git Flow (For scheduled releases)

main (production)
develop (integration)
  └── feature/add-login
  └── release/v1.2.0
  └── hotfix/critical-bug

Rules:

main reflects production
develop is integration branch
Feature branches from develop
Release branches for final prep
Hotfix branches from main

Branch Naming Convention

<type>/<ticket>-<description>

Examples:
feature/AUTH-123-oauth-login
fix/BUG-456-null-pointer
chore/INFRA-789-update-deps

Pull Request Guidelines

PR Title

Follow commit message format:

feat(auth): add OAuth2 login support

PR Description Template

## Summary
Brief description of changes

## Changes
- Change 1
- Change 2

## Testing
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed

## Screenshots (if applicable)

## Related Issues
Closes #123

Review Checklist

Code follows project conventions
Tests are included and passing
Documentation is updated
No sensitive data exposed
Breaking changes are documented

Common Operations

Rebase vs Merge

Use Rebase:

Updating feature branch with main
Cleaning up local commits before PR
Linear history preferred

Use Merge:

Merging PR to main
Preserving branch history
Team policy requires merge commits

Interactive Rebase

# Squash last 3 commits
git rebase -i HEAD~3

# Rebase onto main
git rebase -i main

Undo Operations

# Undo last commit (keep changes)
git reset --soft HEAD~1

# Undo last commit (discard changes)
git reset --hard HEAD~1

# Revert a pushed commit
git revert <commit-hash>

Best Practices

Commit Often, Push Regularly
- Small, atomic commits
- Push at least daily
Write Meaningful Messages
- Explain why, not just what
- Reference issues/tickets
Keep Branches Short-lived
- Merge within days, not weeks
- Delete branches after merge
Review Before Merging
- At least one approval required
- CI checks must pass