git-ops
Git Ops
Overview
Execute git operations safely while producing clear, conventional commit messages and workflow guidance.
When to Use
- Running git commands (status, add, commit, push, pull)
- Generating smart commit messages
- Managing branches and merges
Avoid when:
- The task is unrelated to git operations
Quick Reference
| Task | Load reference |
|---|---|
| Git operations | skills/git-ops/references/git.md |
| Branching Strategies | skills/git-ops/references/branching-strategies.md |
Workflow
- Confirm repository state and intent.
- Load the git operations reference.
- Execute the command safely.
- Provide status summary and next steps.
Output
- Operation result summary
- Suggested follow-ups or warnings
Common Mistakes
- Running destructive commands without confirmation
- Writing non-standard commit messages
More from nickcrew/claude-cortex
python-testing-patterns
Python testing patterns and best practices using pytest, mocking, and property-based testing. Use when writing unit tests, integration tests, or implementing test-driven development in Python projects.
3python-performance-optimization
Python performance optimization patterns using profiling, algorithmic improvements, and acceleration techniques. Use when optimizing slow Python code, reducing memory usage, or improving application throughput and latency.
2code-explanation
Use when explaining code, concepts, or system behavior to a specific audience level - provides a structured explanation workflow with depth control and validation steps.
2typescript-advanced-patterns
Advanced TypeScript patterns for type-safe, maintainable code using sophisticated type system features. Use when building type-safe APIs, implementing complex domain models, or leveraging TypeScript's advanced type capabilities.
2prompt-engineering
Optimize prompts for LLMs and AI systems with structured techniques, evaluation patterns, and synthetic test data generation. Use when building AI features, improving agent performance, or crafting system prompts.
2testing-anti-patterns
Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies
2