菜单
Use when committing or pushing completed work; automates gate-aware conventional commits with optional signing and CI/CD checks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | codex-git-autopilot |
| description | Use when committing or pushing completed work; automates gate-aware conventional commits with optional signing and CI/CD checks. |
| load_priority | on-demand |
Collect files → stage → run pre-commit gate → generate conventional commit → GPG sign → push. Never commits on gate failure, never force pushes.
$codex-git-autopilot or $auto-commit.Automates the commit-push cycle with production-grade safety.
--files list)git add specified filespre_commit_check.py (lint, secret scan, debug check, tests)feat(scope): description)python auto_commit.py --project-root ./ --files src/models/User.js src/routes/user.routes.js
python auto_commit.py --project-root ./ --files src/models/User.js -m "feat(user): add email validation"
python auto_commit.py --project-root ./ --files README.md --dry-run
python auto_commit.py --setup-gpg
NEVER commits if pre-commit gate failsNEVER force pushesRun python auto_commit.py --setup-gpg for interactive guide, or:
winget install GnuPG.GnuPG
gpg --quick-generate-key "your@email.com" rsa4096 sign never
gpg --list-secret-keys --keyid-format=long
git config --global user.signingkey YOUR_KEY_ID
git config --global commit.gpgsign true
gpg --armor --export YOUR_KEY_ID
Paste the exported key in GitHub Settings > SSH and GPG Keys > New GPG Key.
This skill integrates with:
codex-execution-quality-gate/scripts/pre_commit_check.py (CI gate)codex-project-memory/scripts/generate_changelog.py (reads commit history)Use for project memory, decisions, handoffs, genome, knowledge index, changelog, and patterns that must persist across sessions.
Use for frontend, backend, mobile, debugging, security, or specialized engineering work that needs focused domain references and strict boundaries.
Use for prototype, MVP, fullstack feature, from-scratch feature, or multi-domain work that needs a SPEC.md before planning or implementation. Do not use for tiny one-file edits.
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.