eagers-conventions

Standardize Azure DevOps Git workflows with branch naming, commit formats, and PR descriptions.

Updated Feb 2, 2026

Search Tags:#git #workflow #branching #conventions #azure-devops #work-items

Ready to run

npx skills add https://github.com/shellicar/claude-config --skill eagers-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: eagers-conventions
Source: https://github.com/shellicar/claude-config/tree/main/skills/eagers-conventions
Command: npx skills add https://github.com/shellicar/claude-config --skill eagers-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Git conventions for Azure DevOps can be inconsistently applied across teams, leading to fragmented workflows, PR confusion, and misaligned work item tracking. This skill standardizes those conventions for Eagers Automotive, reducing onboarding time and errors.

Core Features & Use Cases

Branching Strategy: Prescribed branching model (main, epic, feature) to streamline PRs and integration.
PR & Work Item Policy: Mandatory PR descriptions and work-item linking formats to ensure traceability.
Workflows & Area Paths: Guidance on area paths, iterations, and PR routing to support release management in Azure DevOps.
Use Case: For a new project, adopt the conventions to ensure all team members follow the same flow and reduce review cycles.

Quick Start

Review the Branching Strategy and implement the PR description format in your Azure DevOps project. Then apply the area path conventions to align with Iterations.

Frequently Asked Questions about eagers-conventions

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

FAQPage Schema

How do I standardize Git branch naming conventions in Azure DevOps?▼

Standardize Git branch naming conventions in Azure DevOps by enforcing prescribed branching rules for main and epic branches. This ensures consistent feature branch naming and streamlines pull request integration across the project.

What should a pull request description include for Azure DevOps work item linking?▼

A pull request description for Azure DevOps work item linking must follow a mandatory layout that ensures traceability. It enforces specific PR description formats to properly link work items and align with area path tracking.

How do I map area paths and iterations in Azure DevOps for release management?▼

Map area paths and iterations in Azure DevOps for release management by applying prescribed area path conventions. This aligns PR routing and work item tracking with your project's iteration schedule to support structured release workflows.

What is the best Git branching strategy for Azure DevOps epic and feature branches?▼

The best Git branching strategy for Azure DevOps epic and feature branches uses a prescribed main, epic, and feature model. This structure streamlines pull requests, clarifies integration paths, and enforces consistent commit message formats.

Why do my Azure DevOps work item links and pull requests lack traceability?▼

Azure DevOps work item links and pull requests lack traceability when mandatory work item linking formats and PR description layouts are not applied. Standardizing these conventions ensures all code changes are properly tracked to their corresponding work items.