一键在 Manus 中运行任何 Skill

git-workflow

星标1

分支0

更新时间2026年4月20日 03:01

Use for branching, commit, PR, merge, rebase, and release discipline. Adapts Git workflow guidance to codex-max multi-repo boundaries.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

manhthien2005

manhthien2005/codex-max

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Git Workflow

Overview

Use git-workflow when the task is mainly about git process rather than code behavior. Examples: branching strategy, commit style, PR hygiene, merge/rebase choice, release steps, or conflict-handling discipline.

Workspace-specific rules

This workspace is multi-repo. Therefore:

Always identify the active repo first
Run git commands only inside the declared git scope repo
Never run git commands in the workspace root unless that root is explicitly the active repo
Keep branch and PR guidance aligned with the repo actually being changed

Use when

Setting up or enforcing branch conventions
Deciding merge vs rebase
Writing commit messages or PR descriptions
Preparing releases or tags
Explaining or improving repo collaboration discipline
Resolving git-process confusion in a multi-repo environment

Core guidance

Branching

Prefer a simple, reviewable workflow unless the repo clearly needs something more complex. Short-lived branches are usually the best default.

Commit messages

Prefer clear, scoped commit messages that explain the intent of the change. A conventional-commit style is acceptable when the repo already uses it.

Merge vs rebase

Rebase is useful for keeping a local feature branch current before review
Merge is safer when preserving shared branch history matters
Avoid rewriting history on shared/protected branches

Pull requests

A good PR should state:

what changed
why it changed
how it was verified
what risks or follow-up work remain

Output contract

When this skill is used, the result should include:

Active git scope
Recommended branch strategy
Commit/PR guidance
Merge/rebase recommendation
Release or rollback notes if relevant

Related skills

verification-before-completion — ensure evidence exists before calling work ready
planning-with-files — when git workflow is part of a larger multi-step task
task-router-lite — routes here when git process is the main subject

同仓库更多 Skills

同仓库

lint-and-validate

manhthien2005/codex-max

MANDATORY: Run appropriate validation tools after EVERY code change. Do not finish a task until the code is error-free.

2026-04-201

planning-with-files

manhthien2005/codex-max

Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring 5+ tool calls. Supports automatic session recovery after /clear.

2026-04-201

systematic-debugging

manhthien2005/codex-max

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

2026-04-201

task-intelligence

manhthien2005/codex-max

Legacy compatibility alias for task-router-lite. Keeps older codex-max references working while using a thin Phase PLAN routing model.

2026-04-201

task-router-lite

manhthien2005/codex-max

Thin Phase PLAN router for codex-max. Select at most one primary execution skill and one optional secondary skill from the installed local skill surface.

2026-04-201

architecture-decision-records

manhthien2005/codex-max

Use when a significant technical decision should be recorded with context, alternatives, and consequences so the reasoning survives beyond the current session.

2026-04-201

name	git-workflow
description	Use for branching, commit, PR, merge, rebase, and release discipline. Adapts Git workflow guidance to codex-max multi-repo boundaries.
risk	safe
source	codex-max
origin	ECC-adapted
date_added	2026-04-19

Git Workflow

Overview

Workspace-specific rules

This workspace is multi-repo. Therefore:

Always identify the active repo first
Run git commands only inside the declared git scope repo
Never run git commands in the workspace root unless that root is explicitly the active repo
Keep branch and PR guidance aligned with the repo actually being changed

Use when

Setting up or enforcing branch conventions
Deciding merge vs rebase
Writing commit messages or PR descriptions
Preparing releases or tags
Explaining or improving repo collaboration discipline
Resolving git-process confusion in a multi-repo environment

Core guidance

Branching

Prefer a simple, reviewable workflow unless the repo clearly needs something more complex. Short-lived branches are usually the best default.

Commit messages

Prefer clear, scoped commit messages that explain the intent of the change. A conventional-commit style is acceptable when the repo already uses it.

Merge vs rebase

Rebase is useful for keeping a local feature branch current before review
Merge is safer when preserving shared branch history matters
Avoid rewriting history on shared/protected branches

Pull requests

A good PR should state:

what changed
why it changed
how it was verified
what risks or follow-up work remain

Output contract

When this skill is used, the result should include:

Active git scope
Recommended branch strategy
Commit/PR guidance
Merge/rebase recommendation
Release or rollback notes if relevant

Related skills

verification-before-completion — ensure evidence exists before calling work ready
planning-with-files — when git workflow is part of a larger multi-step task
task-router-lite — routes here when git process is the main subject