rsg-branching-commiting

Create standardized Git branches and commit messages for RSG repositories.

1|Updated May 7, 2022
One-click install
npx skills add https://github.com/brandonburrus/dotfiles --skill rsg-branching-commiting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rsg-branching-commiting
Source: https://github.com/brandonburrus/dotfiles/tree/main/.config/opencode/skills/rsg-branching-commiting
Command: npx skills add https://github.com/brandonburrus/dotfiles --skill rsg-branching-commiting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating correctly named Git branches and crafting properly formatted commit messages for Republic Services (RSG) projects, ensuring consistency and adherence to established standards.

Core Features & Use Cases

  • Standardized Branch Creation: Generates branches following the US######_snake_case_description or DE######_snake_case_description format.
  • Formatted Commit Messages: Ensures commits are prefixed with the Rally artifact ID and adhere to specific formatting rules.
  • Guided Git Workflow: Assists users through identifying artifact IDs, drafting descriptions, staging files, and committing changes.
  • Use Case: When starting a new feature for a Rally ticket US123456, this Skill helps you create a branch named US123456_implement_user_auth and commit your changes with messages like US123456: implement user authentication middleware.

Quick Start

Use the rsg-branching-commiting skill to create a new branch for artifact US123456 with the description add new feature.

Frequently Asked Questions about rsg-branching-commiting

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

FAQPage Schema
How do I create a Git branch with the correct naming convention for Rally artifacts?

Git commit messages for RSG repositories require a Rally artifact ID prefix followed by a descriptive message. This enforces a clear audit trail linking code changes directly to specific Rally development or user story tickets.

What is the process for staging and committing grouped file changes?

Staging and committing grouped file changes is facilitated through a guided Git workflow that identifies artifact IDs, drafts descriptions, and stages files according to user-defined groupings before committing the changes.

Does this Git workflow support both User Story and Defect Rally artifacts?

Yes, this Git workflow supports both User Story and Defect Rally artifacts by enforcing branch naming conventions that begin with either the US###### or DE###### prefix followed by a snake case description.

How do I enforce a consistent commit message format for Rally artifact IDs?

You enforce a consistent commit message format by prefixing commits with the Rally artifact ID and adhering to specific formatting rules, ensuring every commit message maps directly to its corresponding Rally ticket.