Skip to content

搵技能.../

Agent Skill Search Engine

搜尋

搜尋
分類
職業

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

技能檔案

Commit Work

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

24,709 星標

2026年1月25日

職業
分類: 自動化工具

技能內容

Goal

Make commits that are easy to review and safe to ship:

only intended changes are included
commits are logically scoped (split when needed)
commit messages describe what changed and why

Inputs to ask for (if missing)

Single commit or multiple commits? (If unsure: default to multiple small commits when there are unrelated changes.)
Commit style: Conventional Commits are required.
Any rules: max subject length, required scopes.

Workflow (checklist)

Inspect the working tree before staging
- git status
- git diff (unstaged)
- If many changes: git diff --stat
Decide commit boundaries (split if needed)
- Split by: feature vs refactor, backend vs frontend, formatting vs logic, tests vs prod code, dependency bumps vs behavior changes.

相關技能

快速安裝

Commit Work

npx skillvault add davila7/davila7-claude-code-templates-cli-tool-components-skills-productivity-commit-work-skill-md

下載 Skill 打開源碼倉庫

作者: davila7
星標: 24,709
更新時間: 2026年1月25日
職業

本頁內容

If changes are mixed in one file, plan to use patch staging.

Stage only what belongs in the next commit

Prefer patch staging for mixed changes: git add -p
To unstage a hunk/file: git restore --staged -p or git restore --staged <path>

Review what will actually be committed

git diff --cached
Sanity checks:
- no secrets or tokens
- no accidental debug logging
- no unrelated formatting churn

Describe the staged change in 1-2 sentences (before writing the message)

"What changed?" + "Why?"
If you cannot describe it cleanly, the commit is probably too big or mixed; go back to step 2.

Write the commit message

Use Conventional Commits (required):
- type(scope): short summary
- blank line
- body (what/why, not implementation diary)
- footer (BREAKING CHANGE) if needed
Prefer an editor for multi-line messages: git commit -v
Use references/commit-message-template.md if helpful.

Run the smallest relevant verification

Run the repo's fastest meaningful check (unit tests, lint, or build) before moving on.

Repeat for the next commit until the working tree is clean

Deliverable

Provide:

the final commit message(s)
a short summary per commit (what/why)
the commands used to stage/review (at minimum: git diff --cached, plus any tests run)

02

Inputs to ask for (if missing)

03Workflow (checklist)

軟件開發人員

Git 工作流程

Gh Issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

自動化工具

Coding Agent (bash-first)

Delegate coding tasks to Codex, Claude Code, or Pi agents via background process. Use when: (1) building/creating new features or apps, (2) reviewing PRs (spawn in temp dir), (3) refactoring large codebases, (4) iterative coding that needs file exploration. NOT for: simple one-liner fixes (just edit), reading code (use read tool), thread-bound ACP harness requests in chat (for example spawn/run Codex or Claude Code in a Discord thread; use sessions_spawn with runtime:"acp"), or any work in ~/clawd workspace (never spawn agents here). Claude Code: use --print --permission-mode bypassPermissions (no PTY). Codex/Pi/OpenCode: pty:true required.

Git 工作流程

Security Triage

Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.

Git 工作流程

Openclaw Ghsa Maintainer

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Github

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.

自動化工具

Fix

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

軟件開發人員

Commit Work | Skills Pool