skills.rest
RogerioSobrinho
RogerioSobrinhoCOMMUNITY
Explore all skills by this author →
GitHub

git-workflow

Enforce conventional commit rules and PR workflow practices for Git projects.

Updated Mar 26, 2026
Search Tags:#git#workflow#branching#commits#pull-request#rebasing#merge-conflict
One-click install
npx skills add https://github.com/RogerioSobrinho/codeme-copilot --skill git-workflow-rogeriosobrinho
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-workflow
Source: https://github.com/RogerioSobrinho/codeme-copilot/tree/main/skills/git-workflow
Command: npx skills add https://github.com/RogerioSobrinho/codeme-copilot --skill git-workflow-rogeriosobrinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing git workflows and PR practices is error-prone without standard conventions; this skill provides a guided, repeatable framework.

Core Features & Use Cases

  • Conventional commit rules and ticket-aware branch naming
  • Interactive rebase guidance and clean history maintenance
  • Conflict resolution strategies and bisect workflows
  • Stash management and PR best practices for smooth releases
  • Quick reference examples and context-aware prompts for common scenarios

Quick Start

Apply the conventional commit rules and branch naming patterns to your next change and follow the guided rebase and merge steps to prepare a clean PR.

Frequently Asked Questions about git-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to standardize git branch naming and commit rules for a project?▼

Resolving merge conflicts during an interactive rebase requires targeted conflict resolution strategies and stash management to safely handle local changes. Following guided rebase steps helps maintain clean history and prepares smooth PR releases without losing work.

How do I prepare a pull request for release using a conventional git workflow?▼

Preparing a pull request for release involves applying conventional commit rules, executing interactive rebases to clean history, and verifying PR readiness. This ensures smooth releases by standardizing the git workflow and guiding conflict resolution before merging.

When do I need to use git bisect workflows and stash management?▼

You need git bisect workflows and stash management when tracking down regressions or temporarily shelving changes during complex rebases. These practices maintain clean history and provide safe execution patterns for managing work-in-progress alongside conflict resolution.

Does this git workflow guidance apply to common software engineering contexts?▼

Yes, this git workflow guidance applies to common software engineering contexts by defining frontmatter metadata, command guidance, and safe execution patterns. It covers standard rebase, merge, and stash operations suitable for general software development environments.

Related Skills

Explore More Software Engineering Skills→
winsorllcwinsorllc

git-ops

Automate Git operations for commits, branches, and remote synchronization.

Community
Basic
jaeyeonlingjaeyeonling

git-workflow

Standardize Git workflows with conventional commits and branching strategies.

Community
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced
lushly-devlushly-dev
4

manage-git

Orchestrate Git workflows for branching, releases, and parallel development.

Official
Advanced