メニュー
Use this skill for validated local commit and optional push workflows where scope, staged content, identity, gates, and human confirmation must be handled explicitly.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use this skill for backend API, DTO, or enum changes that require frontend request wrappers, types, enums, or UI adaptations.
Use this skill for durable execution records, runbooks, evidence folders, artifacts, and validation of archive layout after task completion.
Use this skill for desktop productivity UI design systems, design tokens, dense tables, status markers, theme tokens, and non-AI-looking Electron app visual standards.
Use this skill for Electron desktop packaging and release readiness across Windows, macOS, and Linux, including signing boundaries, artifacts, dry-runs, and public release checks.
Use this skill for cross-platform desktop UI QA of Electron apps, including renderer screenshots, native window behavior, shell prerequisites, task logs, and platform-specific checks.
Use this skill for database repair work that must begin with readonly confirmation, prepare minimal SQL for human DMS execution, and verify with readonly post-checks.
| name | commit-guard |
| description | Use this skill for validated local commit and optional push workflows where scope, staged content, identity, gates, and human confirmation must be handled explicitly. |
| os | cross-platform |
Use this Skill when the situation matches the frontmatter description. It is cross-platform and tool-neutral: judgment, sequencing, risk boundaries, and human confirmation points live here; deterministic checks should be delegated to installed workflow runtime paths first, then to source repository paths when the runtime is not installed.
os: cross-platform. The guidance applies to Windows, macOS, and Linux. Shell-specific git quoting must be kept explicit and reported with the final command.
Prefer installed runtime paths:
~/.agent-routines/workflows.agent-routines/workflowsSource fallback:
workflows/<workflow-name>/Recommended workflows: commit-check, gate-check, preflight
Ask before staging broad or ambiguous changes, committing, pushing, rewriting history, creating tags, publishing releases, or using one-off git identity values that are not supported by repo history.
Separate worktree dirtiness, validation failures, missing git identity, protected branch errors, and remote history divergence. Report the smallest safe next step instead of retrying destructive git commands.