AGENT SKILL

commit-push-pr

根據目前工作區的實際變更,完成一次符合 Conventional Commits 的 Git 提交、推送與 Pull Request 建立;適用於要交付完整分支變更的情境。

License 许可
MIT
所属仓库
cdcd72/skills
最近更新
2026-08-12
Stars
★ 0
Forks
0

01 前言 Front Matter

name
commit-push-pr
description
根據目前工作區的實際變更,完成一次符合 Conventional Commits 的 Git 提交、推送與 Pull Request 建立;適用於要交付完整分支變更的情境。

03 SKILL.md 正文

Commit Push PR

目的

根據目前工作區的實際變更,完成一次符合 Conventional Commits 的 Git 提交,推送到遠端倉庫,並建立 Pull Request。

適用時機

  • 需要一次完成提交、推送與 PR 建立
  • 需要根據實際 diff 產出 PR 標題與描述

流程

  1. 檢查目前分支與變更。

    git branch --show-current
    git status -s
    git diff HEAD
    
  2. 根據實際 diff 判斷分支類型、分支名稱與 commit message;若沒有實際變更,停止,不要建立空提交。

  3. 如果目前在 main 分支,先建立新分支。

    git checkout -b <type>/<description>
    
  4. 暫存並確認提交內容。

    git add .
    git status -s
    git diff --cached
    
  5. 建立單一提交。

    git commit -m "<type>(<scope>): <description>"
    
  6. 推送目前分支到遠端。

    git branch --show-current
    git push -u origin <current-branch>
    
  7. 根據實際 diff 與 commit 內容撰寫 Pull Request title 與 description。

  8. 建立 Pull Request。

    gh pr create --base main --title "<title>" --body "<description>"
    

Pull Request 規範

Title

  • 使用與提交訊息相同的 <type>(<scope>): <description> 格式
  • 必須根據實際 diff 撰寫

Description

  • 使用繁體中文
  • 根據實際 diff 撰寫
  • 使用具體且明確的項目清單描述實際變更,並適當分組
  • 不要遺漏相關變更,也不要編造 diff 中不存在的內容
  • 只保留有實際內容的章節
## 變更內容

- ...

## 變更目的

- ...

## 測試項目

- ...

## 注意事項

- ...

限制

  • 只建立一個 commit
  • 不要 amend
  • 不要提交 secrets、.env、建置產物、暫存檔或無關檔案

04 同仓库更多 Skills

cdcd72
cdcd72/skills

template-skill

Replace with description of the skill and when Agent should use it.

★ 0
cdcd72
cdcd72/skills

simple-sdd

simple sdd workflow for coding tasks. use when the user says 提案, 實作, or 歸檔 for a development request, or asks to follow a lightweight sdd process before coding. enforce proposal before implementation, wait for confirmation, complete one task at a time, report after each small step, and archive completed sdd work.

★ 0
cdcd72
cdcd72/skills

presentation-flow-writer

Guides the user through co-authoring a "簡報流程檔" (presentation flow document) — a structured input document written FOR a slide-generation AI agent, not a script or final slide copy — then turns it into a client-facing HTML review page. Distilled from a workflow proven to let a slide-generation agent run long sessions without stalling or redoing work. Use when the user wants to plan a talk/deck's narrative before generating slides, asks to design a "簡報流程" / "簡報大綱" / "投影片流程檔", wants a template for briefing a presentation-generation AI, or asks to turn an existing 簡報流程檔 into something a client can review and sign off on ("給客戶看的版本" / "簡報流程確認版" / HTML 確認頁).

★ 0
cdcd72
cdcd72/skills

merge-branch

Merge one local Git branch into another through a guarded workflow: inspect repository state, fetch remote references, analyze divergence, perform the local merge, resolve conflicts according to both branches' intent, run project validation, and report the result. Use when the user asks to merge source branch X into target branch Y, integrate one branch into another, or resolve conflicts caused by that local branch merge. Operate only with local Git commands. Never handle pull requests or merge requests. Never push unless the user gives a separate explicit instruction after reviewing the local result.

★ 0
cdcd72
cdcd72/skills

implementation-orchestrator

Turn engineering work into a reviewed execution baseline with a context pack, implementation plan, complexity routing, optional workstream breakdowns, execution briefs for coding agents or human executors, QA verification, and optional delivery updates. Use when the user wants to turn a bug, feature, refactor, review request, or technical task into an implementation plan, coordinate work across coding agents or human executors, or verify completed implementation against the approved plan.

★ 0
cdcd72
cdcd72/skills

gemma4-prompt-engineer

Based on the official Gemma 4 documentation and a curated practical knowledge base, assist in writing, optimizing, and diagnosing prompts tailored for the Google Gemma 4 model. When a user mentions Gemma 4 (including any of its sizes, such as E2B, E4B, 12B, 26B A4B, or 31B), needs to write/modify a Gemma 4 prompt, or asks about Gemma 4 control tokens, thinking mode, multimodal ordering, tool/function calling formats, or why an existing Gemma 4 prompt is underperforming, you must utilize this Skill rather than relying solely on general prompting knowledge.

★ 0