菜单
Git command rules, commit message conventions, and safe usage patterns. Use when the user asks to commit, create a branch, check differences, write a commit message, or perform any git operation. Also use when discussing version control workflows or git safety.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Code review principles and checklist for reviewing any codebase regardless of language. Use when the user asks to review code, perform a code review, assess a pull request, or evaluate code quality across design, tests, performance, security, and correctness.
Planning skill for complex, multi-session work. Use when the user enters plan mode, asks to plan a feature, design a system, create a workspace, write a design doc, or when the problem requires structured analysis before implementation.
Test Driven Development methodology with acceptance tests and unit tests. Use when the user asks to write tests, add test coverage, implement a feature using TDD, create a failing test first, or when discussing red-green-refactor, test-first development, or test strategy.
Code quality principles for writing clean, maintainable software. Use when reviewing code, refactoring, discussing best practices, improving readability, reducing complexity, or when the user mentions code quality, clean code, SOLID, DRY, or maintainability.
.NET Software Engineer persona using TDD, Domain Driven Design, and C#. Use when working on .NET, C#, F#, ASP.NET, or dotnet projects, or when the user asks about software architecture, domain modeling, clean architecture, hexagonal architecture, or DDD patterns like aggregates, value objects, entities, and repositories.
Rust Software Engineer persona using TDD, Domain Driven Design, and Rust. Use when working on Rust, Cargo, or crate projects, or when the user asks about software architecture, domain modeling, clean architecture, hexagonal architecture, or DDD patterns like aggregates, value objects, entities, and repositories.
基于 SOC 职业分类
| name | git-conventions |
| description | Git command rules, commit message conventions, and safe usage patterns. Use when the user asks to commit, create a branch, check differences, write a commit message, or perform any git operation. Also use when discussing version control workflows or git safety. |
Rules for safe and consistent git usage.
Before committing, the code must compile and tests must be successful without failing / ignored tests.
push.force --force.A git commit message must start with:
feat: for featurefix: when fixing the codebaserefac: for refactoring, mostly to prepare or finish a featchore: to cleanup the codebase, removing dead codedoc: when touching to .md files or documentationtest: when touching test only