agentsclimarketplace

Fix git issues

Skill emaraschio/cursor-commands/plugin/.cursor/skill-contracts/fix-git-issues

Production-grade Cursor slash commands with paired skill contracts, behavioral evals, and ship-gate CI. Install as a user plugin.

Install
npx -y skills add emaraschio/cursor-commands --skill fix-git-issues

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Diagnose and fix git state problems

SKILL.md

1.6 KB, as published. Nobody here has run it

Overview

Help resolve common Git problems and conflicts with step-by-step commands and explanations for each situation.

Steps

  1. Merge Conflicts
    • Analyze conflicting changes and their context
    • Provide resolution strategies for different conflict types
    • Suggest the best approach to preserve important changes
    • Generate resolved code maintaining functionality
  2. Branch Management
    • Help with branch cleanup and organization
    • Suggest rebasing vs merging strategies
    • Assist with cherry-picking specific commits
    • Guide through complex branch operations
  3. Commit History
    • Help with commit message improvements
    • Assist with squashing and organizing commits
    • Guide through interactive rebase operations
    • Fix commit authorship and metadata
  4. Repository Issues
    • Help recover from detached HEAD state
    • Assist with undoing commits and changes
    • Guide through stash management
    • Resolve submodule and remote issues

Git Issues Checklist

  • Problem identified and analyzed
  • Git commands provided with explanations
  • Resolution strategy validated
  • Changes tested and verified
  • Repository state clean and functional

Guardrails

  • Get explicit consent before destructive git commands (reset, rebase, or history rewrite).
  • Never force-push main or a shared branch without an explicit request.
  • Explain each command before running it.
  • Never print or commit secrets or credential files (.env, .env.*, keys); flag any exposure instead of committing it.

Gives 0 of the 12 instructions most pr commit review skills give

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

  • use conventional commits formatin 123 of 888, across 110 files
  • keep subject line under 72 charactersin 60 of 888, across 46 files
  • delete branches after mergein 50 of 888, across 37 files
  • use imperative mood in subject linein 50 of 888, across 41 files
  • use imperative mood in commit messagesin 45 of 888
  • generate a conventional commit messagein 42 of 888
  • make atomic commitsin 37 of 888, across 25 files
  • run tests before committingin 36 of 888, across 24 files
  • run project test suite to verify clean baselinein 35 of 888, across 7 files
  • run detected project setup commandsin 34 of 888, across 6 files
  • wrap commit body at 72 charactersin 32 of 888, across 25 files
  • split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

  • provide git commands with explanations
  • validate the resolution strategy
  • test and verify changes
  • ensure repository state is clean
  • get explicit consent before destructive git commands
  • explain each command before running it

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.