---
name: git-workflow
description: | Use when this capability is needed. git diff --name-only git add <file1> <file2> <type>: <desc…
category: engineering
runtime: no special runtime
---

# git-workflow output preview

## PART A: Task fit
- Use case: | Use when this capability is needed. git diff --name-only git add <file1> <file2> <type>: <description> git commit -m "提交信息" git config --global user.name "Your Name" runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “核心指令 / 第一步：检测文件变更 / 第二步：添加文件” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “| Use when this capability is needed. git diff --name-only git add <file1> <file2> <type>: <description> git commit -m "提交信息" git config --global user.name "Your Name" runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “核心指令 / 第一步：检测文件变更 / 第二步：添加文件” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.