菜单
Git operations, branching strategies, commit conventions, and repository management. Use when working with version control, creating branches, writing commits, or resolving merge conflicts.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
AWS CLI best practices including pagination control, output formatting, and efficient querying. Use when running AWS CLI commands, querying AWS resources, or automating AWS operations.
AWS CloudWatch dashboard observability patterns including dashboard hierarchy, widget selection, CDK implementation, metric math, alarms, and cross-account monitoring. Use when creating dashboards, setting up observability, or instrumenting workloads with CloudWatch.
Docker image building best practices including multi-stage builds, layer optimization, and security hardening. Use when creating Dockerfiles, optimizing image size, or debugging container builds.
Technical documentation patterns including READMEs, API docs, runbooks, and architecture decision records. Use when writing documentation, creating runbooks, or documenting system architecture.
Bash and Zsh scripting patterns with built-in logging and non-interactive execution. Use when writing automation scripts, CLI tools, or system administration tasks.
| name | git-workflow |
| description | Git operations, branching strategies, commit conventions, and repository management. Use when working with version control, creating branches, writing commits, or resolving merge conflicts. |
<type>(<scope>): <subject>
[optional body]
[optional footer]
Types: feat, fix, docs, style, refactor, test, chore
Good: feat(auth): add OAuth2 support for GitHub login
Bad: fixed stuff
<type>/<ticket>-<description>
Examples:
feature/PROJ-123-user-authenticationfix/PROJ-456-null-pointer-crashhotfix/PROJ-789-security-patch# Interactive rebase to clean up commits
git rebase -i HEAD~3
# Squash last N commits
git reset --soft HEAD~N && git commit
# Cherry-pick specific commit
git cherry-pick <sha>
# Undo last commit (keep changes)
git reset --soft HEAD~1
# Find commit that introduced bug
git bisect start
git bisect bad HEAD
git bisect good <known-good-sha>
git status — identify conflicted files<<<<<<<, =======, >>>>>>>git add <file> then git rebase --continue or git merge --continueAlways run before pushing: