Run any Skill in Manus with one click

Get Started

git-workflow

Stars1

Forks0

UpdatedJune 18, 2026 at 02:18

Git workflow: branches, PR, merge, cleanup

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

aAAaqwq

aAAaqwq/openclaw-team

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	git-workflow
description	Git workflow: branches, PR, merge, cleanup

Git Workflow

Standard Git workflow: branches, commits, PR, merge

When to use

Any change to data or code going to GitHub
"commit" / "push" / "create PR" / "merge"
After running any skill that modifies files

Rules

1. Never push to main directly

Always through PR:

git checkout -b <prefix>/<name>
# changes
git add <files>
git commit -m "Description"
git push -u origin <prefix>/<name>
gh pr create --title "..." --body "..."
gh pr merge --squash --delete-branch
git checkout main && git pull

2. Branch naming

Change type	Prefix	Example
New feature	`feature/`	`feature/clientk-lookalikes`
Data update	`update/`	`update/stream-cohort-2026-02-08`
Fix	`fix/`	`fix/crm-product-fk`
New lead/contact	`feat/`	`feat/kyrylo-mazur-lead`

3. Merge strategy

Always squash merge + delete branch:

gh pr merge --squash --delete-branch

--squash -- one clean commit in main
--delete-branch -- automatically deletes the branch after merge

4. After merge

git checkout main
git pull origin main

5. Commit message format

<Action>: <what exactly was done>

Details if needed.

Co-Authored-By: Claude <noreply@anthropic.com>

Examples:

Add 24 stream participants (p-fb-018..041)
Update task-042: expand stream outreach to 39 people
Fix CRM product FK consistency

6. Cleanup

If old branches have accumulated:

# View all remote branches
gh api repos/your-org/<repo>/branches --jq '.[].name'

# Delete a specific one
gh api repos/your-org/<repo>/git/refs/heads/<branch> -X DELETE

Repositories

Repo	What's there	Prefix
`your-org/$PROJECT_ROOT`	CRM + PM data	`update/`, `feat/`, `fix/`
`your-org/claude-skills`	Claude skills	`update/`, `feature/`
`your-org/google-tools`	Google API scripts	`feature/`, `fix/`

Restrictions

DO NOT commit secrets (.env, token.json, credentials.json)
DO NOT force push
DO NOT rebase main
DO NOT leave dead branches after merge

Related skills

change-review -- CRM/PM data validation before PR
code-review -- code review for code PRs

More from this repository

same repository

baxia-sales-suite

aAAaqwq/openclaw-team

霸下销售总监大师技能包 — 全球顶尖B2B销售能力。对标华为铁三角+Salesforce+麦肯锡谈判法。

2026-06-181

mobai-creative-direction-suite

aAAaqwq/openclaw-team

墨白首席美学官大师技能包 — 全球顶级视觉战略能力。对标伦敦皇家艺术学院 + 奥美全球 + 苹果Jony Ive设计标准。

2026-06-181

ai-coding-fleet

aAAaqwq/openclaw-team

轩辕AI编码舰队——OpenClaw作为大脑，指挥Claude Code/Cursor/Windsurf/Trae/Codex CLI集群并行开发。覆盖：ACP配置、IDE接入、权限管理、任务分发、windsurf+cursor双IDE调度、worktree隔离、舰队看板。触发词：IDE舰队、编码集群、AI IDE、多工具编排、ACP配置、Cursor舰队、Windsurf集群、Trae接入、IDE调度、并行编码、AI编码引擎、IDE编排、coding fleet

2026-06-181

project-sdlc-tracker

aAAaqwq/openclaw-team

项目进度追踪与SDLC全周期管理——ETA承诺、实时看板、风险预警、多项目并行调度。覆盖：任务拆解协议、ETA估算模型、进度追踪机制、日报/周报模板、风险预警系统、承诺驱动开发。触发词：项目进度、SDLC、ETA、甘特图、看板、燃尽图、里程碑、进度追踪、project management、进度汇报、阻塞告警

2026-06-181

vibecoding-master

aAAaqwq/openclaw-team

2025年最前沿的AI原生开发范式——VibeCoding。覆盖：Prompt-to-Product工作流、多轮对话管理、AI编码助手协作策略、代码质量保障、v0.dev/Lovable/Claude Code/Replit Agent工具链集成。触发词：vibecoding、VibeCoding、AI原生开发、提示即产品、AI pair programming、conversation-driven coding、prompt engineering for products

2026-06-181

feishu-doc-optimizer

aAAaqwq/openclaw-team

飞书云文档内容优化与格式美化。当用户需要优化飞书文档的排版、结构、格式、美观度时使用此技能。支持：(1) 读取飞书文档内容 (2) 优化文档结构和层次 (3) 清空并替换文档内容 (4) 通过浏览器自动化编辑文档。触发词：优化飞书文档、美化文档、整理文档格式、文档排版。

2026-06-181

name	git-workflow
description	Git workflow: branches, PR, merge, cleanup

Git Workflow

Standard Git workflow: branches, commits, PR, merge

When to use

Any change to data or code going to GitHub
"commit" / "push" / "create PR" / "merge"
After running any skill that modifies files

Rules

1. Never push to main directly

Always through PR:

git checkout -b <prefix>/<name>
# changes
git add <files>
git commit -m "Description"
git push -u origin <prefix>/<name>
gh pr create --title "..." --body "..."
gh pr merge --squash --delete-branch
git checkout main && git pull

2. Branch naming

Change type	Prefix	Example
New feature	`feature/`	`feature/clientk-lookalikes`
Data update	`update/`	`update/stream-cohort-2026-02-08`
Fix	`fix/`	`fix/crm-product-fk`
New lead/contact	`feat/`	`feat/kyrylo-mazur-lead`

3. Merge strategy

Always squash merge + delete branch:

gh pr merge --squash --delete-branch

--squash -- one clean commit in main
--delete-branch -- automatically deletes the branch after merge

4. After merge

git checkout main
git pull origin main

5. Commit message format

<Action>: <what exactly was done>

Details if needed.

Co-Authored-By: Claude <noreply@anthropic.com>

Examples:

Add 24 stream participants (p-fb-018..041)
Update task-042: expand stream outreach to 39 people
Fix CRM product FK consistency

6. Cleanup

If old branches have accumulated:

# View all remote branches
gh api repos/your-org/<repo>/branches --jq '.[].name'

# Delete a specific one
gh api repos/your-org/<repo>/git/refs/heads/<branch> -X DELETE

Repositories

Repo	What's there	Prefix
`your-org/$PROJECT_ROOT`	CRM + PM data	`update/`, `feat/`, `fix/`
`your-org/claude-skills`	Claude skills	`update/`, `feature/`
`your-org/google-tools`	Google API scripts	`feature/`, `fix/`

Restrictions

DO NOT commit secrets (.env, token.json, credentials.json)
DO NOT force push
DO NOT rebase main
DO NOT leave dead branches after merge

Related skills

change-review -- CRM/PM data validation before PR
code-review -- code review for code PRs