Generate Conventional Commits messages and guide git workflows.
npx skills add https://github.com/softmg/product-tracker --skill git-helper-softmg
Please help me install this Agent Skill. Skill: git-helper Source: https://github.com/softmg/product-tracker/tree/main/.cursor/skills/git-helper Command: npx skills add https://github.com/softmg/product-tracker --skill git-helper-softmg
Many developers struggle to write clear, Conventional Commits messages and to safely perform everyday git workflows such as creating branches, updating from main, resolving conflicts, and investigating history; this Skill provides concise, actionable guidance and templates to reduce mistakes and maintain a clean repo history.
Ask the skill to generate a Conventional Commits message for your staged changes and recommend the appropriate branch command and safety steps.
High-intent search queries and answers about installing and using this skill.
To generate a conventional commit message, the skill analyzes your staged changes and produces a formatted message with a suggested type and scope. It ensures your commit history follows conventional commits standards automatically.
The best way to resolve git merge conflicts is to follow step-by-step conflict resolution guidance provided by the skill, which walks you through identifying conflict markers, resolving discrepancies, and completing the merge safely.
Choosing between git merge and rebase depends on whether you need to preserve merge history or maintain a linear timeline; the skill provides best-practice commands and safety checks to help you avoid rewriting shared history during branch syncing.
To safely undo a git commit without rewriting shared history, use non-destructive patterns like git revert instead of reset; the skill offers specific undo guidance to reverse changes while preserving remote branch integrity.
Using git bisect involves binary searching through your commit history to isolate the offending commit; the skill provides actionable bisect workflows to help you systematically narrow down and identify the exact change that introduced a regression.
Cherry-picking a commit safely involves applying a specific commit's changes to another branch while managing potential conflicts; the skill outlines cherry-pick workflows and safety steps to ensure clean application across branches.
mhattingpeteStage, commit, and push code changes with conventional commit messages.
VYRE-StudiosCommit staged changes, push the branch, and open a pull request via GitHub CLI.
netresearchStandardize Git branching, commit conventions, and PR workflows across teams.
deadlock-mod-managerRebases Git feature branches onto latest default branch, managing conflicts automatically where possible.
