git-ops

Included with Lifetime

$97 forever

Get information about the state of a git repo, get diffs, make commits, make PRs, etc.. Use this skill when the user needs to accomplish git tasks.

General

What this skill does


# Git & GitHub Workflow

## User Confirmation Required

**Use `AskUserQuestion` before these potentially destructive operations**:
- Creating commits (`git commit`)
- Pushing to remote (`git push`)
- Creating pull requests (`gh pr create`)
- Merging PRs (`gh pr merge`)
- Any destructive operation (hard reset, force push, delete branch)

**No confirmation needed for read-only or local operations**:
- `git status`, `git diff`, `git log`, `git branch`
- `git add` (staging)
- `git checkout`, `git switch` (switching branches)
- `git fetch`
- `gh pr view`, `gh pr list`, `gh issue list`

## Conventions

### Commits
- Messages: 1-2 sentences describing the change
- If many changes, break into multiple atomic commits
- Use imperative mood ("Add feature" not "Added feature")
- Never use `--amend` unless explicitly requested

### Branches
- Simple hyphenated names describing purpose
- Examples: `add-user-auth`, `fix-null-pointer`, `refactor-api-client`

### Pull Requests
- Title: concise summary of the change
- Description must include:
  1. **What**: Simple explanation of changes
  2. **Testing**: How changes were tested
  3. **Deploy**: Steps to deploy

## Common Workflows

### Check repo state
```bash
git status
git log --oneline -10
git branch -a
```

### View diffs
Staged changes (ready to commit):
```bash
git diff --cached          # full diff
git diff --cached --stat   # summary
```

Unstaged changes (modified but not staged):
```bash
git diff                   # full diff
git diff --stat            # summary
```

All changes in current branch vs base (for PR context):
```bash
git diff main...HEAD --stat   # summary
git diff main...HEAD          # full diff
git log main..HEAD --oneline  # commits that would be in PR
```

### Create a commit
```bash
git add <files>
git commit -m "Commit message here."
```

For multi-line messages:
```bash
git commit -m "$(cat <<'EOF'
Short summary of changes.

Additional context if needed.
EOF
)"
```

### Create a branch and PR
```bash
git checkout -b descriptive-branch-name
# ... make changes and commits ...
git push -u origin HEAD
gh pr create --title "Title here" --body "$(cat <<'EOF'
## Description

Brief description of changes.

## Testing

How this was tested.

## Deployment

Steps to deploy this change.
EOF
)"
```

### Get PR info
```bash
gh pr view --json number -q .number  # get PR number for current branch
gh pr list                            # list open PRs
```

### Review a PR
```bash
gh pr view <number>
gh pr diff <number>
gh pr checks <number>
gh api repos/{owner}/{repo}/pulls/<number>/comments  # view PR comments
gh pr review <number> --approve
gh pr review <number> --request-changes --body "Feedback here"
```

### Merge a PR
```bash
gh pr merge <number> --squash --delete-branch
```

### Working with issues
```bash
gh issue list
gh issue view <number>
gh issue create --title "Title" --body "Description"
gh issue close <number>
```

## Safety Rules

- Never force push to main
- Never use `--no-verify` unless explicitly requested
- Never amend commits that have been pushed
- Always verify before destructive operations (hard reset, etc.)
- Prefer merge commits over rebases to preserve history
- Flag potential secrets or sensitive files before committing (.env, credentials, API keys)

Files: 1

Size: 3.5 KB

Complexity: 12/100

Category: General

Source: https://github.com/daturkel/dt-cc/tree/main/plugins/dt-git/skills/git-ops

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts