hopeventures-conventions

Standardize Git conventions for Hope Ventures on Azure DevOps.

Updated Feb 2, 2026

Search Tags:#git #conventions #Azure DevOps #branch-naming #commit-messages #pr-guidelines #work-item-linking

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes Git conventions for Hope Ventures on Azure DevOps, ensuring consistent messaging, PR processes, and branch practices across teams.

Core Features & Use Cases

PR description guidelines: ensure clear summaries and linkage to work items.
Branch naming rules: enforce feature, fix, and main branches naming formats.
Commit message rules: enforce imperative mood and concise messages.
Detection logic: automatically determine when the active conventions should apply based on repository URL and workspace context.

Quick Start

Connect to the Hope Ventures Azure DevOps project and start creating PRs that follow the branch naming, commit message, and PR description guidelines.

Frequently Asked Questions about hopeventures-conventions

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

FAQPage Schema

How do I enforce consistent Git branch naming conventions across Azure DevOps repositories?▼

Standard Git branch naming conventions for Azure DevOps repositories are enforced by applying specific rules for feature, fix, and main branches using standard Git tooling and the Azure DevOps CLI.

What are the best commit message rules to standardize for an Azure DevOps workflow?▼

Standard commit message rules for an Azure DevOps workflow enforce imperative mood and concise messaging to maintain consistent Git practices across all team repositories.

How do I link Azure DevOps work items in PR descriptions automatically?▼

You link Azure DevOps work items in PR descriptions by applying PR description guidelines that ensure clear summaries and direct linkage to work items within your Git workflow.

Do I need the Azure DevOps CLI to apply Git conventions for branch naming and commit messages?▼

Yes, applying Git conventions for branch naming, commit messages, PR descriptions, and work-item linking across repositories requires standard Git tooling and the Azure DevOps CLI.

When should Git conventions automatically apply to a repository in Azure DevOps?▼

Git conventions automatically apply to an Azure DevOps repository when detection logic evaluates the repository URL and workspace context to determine if the active conventions should be enforced.

Can I use standard Git tooling to standardize pull request guidelines across multiple Azure DevOps projects?▼

You can use standard Git tooling and the Azure DevOps CLI to standardize pull request guidelines across multiple Azure DevOps projects, ensuring consistent PR processes and work-item linking.