菜单
Git operations wrapper: sync, stage, commit, push. Generates Conventional Commits messages with .scratch artifact references. Use when the user says gitops, commit, push, sync code, or needs version control operations.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | gitops |
| description | Git operations wrapper: sync, stage, commit, push. Generates Conventional Commits messages with .scratch artifact references. Use when the user says gitops, commit, push, sync code, or needs version control operations. |
Git version control operations for the aiops delivery chain.
Pull latest from remote. Default strategy: rebase.
git pull --rebase
If merge conflict: report to user, do not auto-resolve.
Show current working tree state.
git status
git diff --stat
Stage files for commit. Supports selective staging.
git add <files>
Create commit with Conventional Commits message.
Format:
<type>(<scope>): <subject>
<body>
Refs: .scratch/<feature-slug>/
Types: feat | fix | refactor | test | docs | chore
Message generation:
.scratch/<feature>/NOTES.md for design context.scratch/<feature>/REVIEW.md to confirm review passedPre-commit checks:
Push to remote. Requires user confirmation.
git push origin <branch>
Branch management: create, switch, list.
git checkout -b <branch> # create + switch
git checkout <branch> # switch
git branch # list
sync — pull lateststatus — review changesstage — select filescommit — with generated messagepush — after user confirms.scratch/<feature>/REVIEW.md exists and verdict is REQUEST_CHANGES, block commit and reportDelivery overlay — orchestrates lean ladder, tdd, prune, review with sub-phase gates; commits only on user approval.
Flow Conductor for the aiops bundle. One entry — infers task type, shows plain-language steps, tracks journey in flow.state.yaml, dispatches skill + agent per phase.
Structured design process for the architect agent. Guides from grill conclusions to complete NOTES.md + tech-spec.md plus needed domain documentation updates through constraint gathering, module identification, interface design, alternative exploration, and risk analysis. Use when the architect needs to produce design decisions and technical specifications.
Build and query a persistent code graph for the target project. Uses graphify (Tree-sitter + Louvain clustering) for deterministic structural extraction, then the model adds semantic annotations. Use when the user says build graph, code graph, dependency graph, impact analysis, or when other skills need structured code understanding before proceeding.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Use when the user says architecture review, codebase health, deepening, refactor suggestions, or complains about architectural friction.
Review in three modes — code (diff vs standards/spec), design (NOTES + tech-spec before planning), drift (implementation vs tech-spec before ship). Pick mode from Flow Conductor phase or user intent; do not mix artifact types.