skills.rest
hanzlahabib
hanzlahabibCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

rcode-git-flow

Coordinate Git branching and commit workflows for rcode projects.

2|1|Updated Apr 10, 2026
Search Tags:#git#version control#conventional commits#branching#pull requests#merge conflicts#feature branches
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-git-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rcode-git-flow
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/actions/4-implementation/rcode-git-flow
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-git-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the guesswork from Git-based collaboration by standardizing how branches, commits, pull requests, and conflict resolution should work in rcode projects.

Core Features & Use Cases

  • Branching Strategy: Creates feature, fix, and docs branches from the latest main branch with consistent naming rules.
  • Commit and PR Discipline: Uses Conventional Commits, requires issue-closing footers, and keeps pull request titles and bodies aligned with the tracked work.
  • Conflict Handling: Guides careful merge conflict resolution, testing after merges, and safe follow-up commits without rewriting shared history.
  • Use Case: When a developer starts a new issue, this Skill helps them branch correctly, commit in small steps, open the right PR, and merge without breaking repository policy.

Quick Start

Ask the assistant to prepare a compliant rcode Git workflow for your issue, including the branch name, commit plan, pull request text, and merge-safe next steps.

Frequently Asked Questions about rcode-git-flow

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

FAQPage Schema
How do I standardize Git branching and commit workflows for feature development?▼

Standardize Git branching and commit workflows by enforcing consistent branch naming from the latest main branch, applying Conventional Commits, and linking pull request closures to tracked issues within an Epic→Feature→Task hierarchy.

What is the best way to resolve merge conflicts without rewriting shared Git history?▼

Resolve merge conflicts safely by carefully handling conflict markers, running tests immediately after merging, and creating follow-up commits to preserve shared repository history without force pushes or rewrites.

How do Conventional Commits improve pull request discipline in version control?▼

Conventional Commits improve pull request discipline by enforcing standardized commit messages and requiring issue-closing footers, keeping PR titles and bodies strictly aligned with the tracked feature or bug fix work.

Does this Git workflow approach require a specific project hierarchy for bug fixes and docs?▼

Yes, this Git workflow operates within an Epic→Feature→Task hierarchy, applying standardized branching, commit rules, and PR guardrails specifically to feature development, bug fixes, and documentation changes.

Why do I need push-approval guardrails for feature branches?▼

Push-approval guardrails protect repository integrity by preventing unauthorized pushes to shared branches, ensuring that merge conflicts are resolved, tests pass, and pull requests meet closure policy before integration.

Related Skills

Explore More Software Engineering Skills→
mpazarynampazaryna
1

push

Stage, commit, and push Git changes with conventional commit messages.

Community
Intermediate
JacobPEvansJacobPEvans
3

refresh-repo

Synchronize a local Git repository and check open Pull Requests for merge readiness.

Community
Intermediate
mindroom-aimindroom-ai
232

pr-review

Review pull request code for cleanliness, structure, and documentation quality.

Official
Advanced
dnvitidnviti
10

release

Automate semantic versioning, changelog generation, and git tagging for software releases.

Community
Advanced