Git 工作流程

來源狀態

可用來源

原始名稱: git-workflow-and-versioning

原始作者: Addy Osmani

這是第三方 Community Skill；2lus 收錄不代表已完整安全審計或保證安全。

資源類型

Skill

與類似 Skill 有什麼不同？

• GitHub Issues 工作流程教學

  GitHub Issues Workflow 整理議題追蹤與協作；Git Workflow 整理分支、提交與衝突處理。

來源描述的能力

這些是來源描述的可能操作，不代表 2lus 已授予權限或已測試。

尚未列出能力，請審查原始來源。

這個 Skill 是什麼？

讓提交邊界對應單一意圖，保留可追溯與回復能力。

可以做什麼？何時適合使用？

• 拆分混合修改
• 規劃短生命週期分支
• 分析 merge 或 rebase 衝突

如何使用

1. 先讀取工作樹與團隊規範
2. 按修復、重構與格式化分組
3. 提出提交順序與衝突處理計畫，等待寫入授權

使用前你需要準備

• 目標工作流程與現況
• 可執行操作的授權界線

你可以替換：

[target branch]、[workflow]

環境與相依需求

• 需要 diff、分支關係與既有 commit 慣例；使用完整來源參考。

使用範例與 Prompt

以下是 2lus 撰寫的示範需求；請替換為你有權處理的檔案與專案，不代表已執行或保證結果。

入門

閱讀這份 diff，建議三個可獨立審查的 commit 邊界，不要建立 commit。

實務

將重構、bug fix 與 formatting 分開，列出各自依賴與建議 commit message。

進階

分析 feature 分支的衝突，比較 merge 與 rebase 對共享歷史的影響；只提供安全處理步驟。

實用提醒

• 每個 commit 說明原因，不只描述檔案變動。

限制與注意事項

• 提交拆分不會證明行為正確；不能自行重寫共享歷史。

安全注意事項

• 先保留使用者未提交修改；push、force push、reset 與刪分支須明確授權。

使用與設定

此條目不提供已確認的通用安裝指令；請依官方文件與 Agent 版本操作。

支援平台

未確認特定 Agent 相容性

來源與授權

來源查核日期（非安全認證）: 2026-09-29

MIT

相關 Skills

• GitHub Issues 工作流程教學
• 發布工程

Source status

Active source

Original name: git-workflow-and-versioning

Original author: Addy Osmani

This is a third-party community skill. Inclusion by 2lus is not a complete security audit or safety guarantee.

Resource type

Skill

How is this different from similar skills?

• GitHub Issues Workflow

  GitHub Issues Workflow organizes issue tracking and collaboration; Git Workflow organizes branches, commits and conflicts.

Documented capabilities

These are operations described upstream, not permissions granted or tested by 2lus.

Capabilities not declared here; review the original source.

What is this skill?

Align commits with single intentions while preserving traceability.

Use cases and when to use it

• Split mixed changes
• Plan short-lived branches
• Analyze merge or rebase conflicts

How to use it

1. Inspect the working tree and team policy
2. Group fixes, refactors and formatting
3. Propose commit order and obtain write authorization

What you need

• Target workflow and current state
• Authorization boundaries

You can replace:

[target branch], [workflow]

Environment and dependencies

• Provide diffs, branch relationships and commit conventions; retain source references.

Usage and prompt examples

These example requests were written by 2lus. Substitute files and projects you may use; examples are not executed results or guarantees.

Beginner

Read this diff and propose three independently reviewable commit boundaries without committing.

Practical

Separate refactoring, bug fixes and formatting; identify dependencies and draft commit messages.

Advanced

Compare merge and rebase for this shared feature branch conflict; provide safe steps without rewriting history.

Tips

• Explain why each commit exists, not merely which files changed.

Limitations

• Commit structure cannot prove correctness or justify rewriting shared history.

Security notes

• Preserve uncommitted work; pushing, resets and branch deletion require authorization.

Usage and setup

No verified universal installation command is provided for this entry. Follow the official documentation for your agent version.

Supported agents

Specific agent compatibility unknown

Sources and license

Source check date (not a safety certification): 2026-09-29

MIT

Related skills

• GitHub Issues Workflow
• Release Engineering