Use when performing git operations or generating smart commit messages - provides safe git workflow guidance, validation checks, and conventional commit formatting.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add NickCrew/Claude-Cortex --skill git-ops --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Git Ops?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/nickcrew-git-ops-claude-cortex)More formats (shields.io, HTML) on the badges page.
---
name: git-ops
description: Use when performing git operations or generating smart commit messages - provides safe git workflow guidance, validation checks, and conventional commit formatting.
keywords:
- conventional commit
- git branch
- git commit
- git pull
- git push
- git status
- merge conflict
- rebase
- smart commit
file_patterns:
- '**/.git/worktrees/**'
- '**/worktrees/**'
confidence: 0.72
---
# 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
1. Confirm repository state and intent.
2. Load the git operations reference.
3. Execute the command safely.
4. 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
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.