skills.rest
shellicar
shellicarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

flightrac-conventions

Enforce Git and PR conventions for Flightrac projects on Azure DevOps.

Updated Feb 2, 2026
Search Tags:#git#conventions#pull-requests#branch-naming#azure-devops#work-items
One-click install
npx skills add https://github.com/shellicar/claude-config --skill flightrac-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flightrac-conventions
Source: https://github.com/shellicar/claude-config/tree/main/skills/flightrac-conventions
Command: npx skills add https://github.com/shellicar/claude-config --skill flightrac-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines and enforces Git and PR conventions for Flightrac projects on Azure DevOps to ensure consistent collaboration and traceability across repositories.

Core Features & Use Cases

  • PR guidelines: Standard PR description format and required work item references.
  • Commit standards: Naming conventions and branch naming rules.
  • Detection & platform: Guidance for Azure DevOps workflows and item linking.
  • Use Case: A Flightrac team ensures every PR includes a linked Azure DevOps work item and consistent commit messages.

Quick Start

Apply the Flightrac conventions to new and existing Azure DevOps repositories by enabling the standard branch naming and PR description formats.

Frequently Asked Questions about flightrac-conventions

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

FAQPage Schema
How do I enforce Azure DevOps PR conventions for branch naming and work items?▼

Azure DevOps PR conventions are enforced by applying standard branch naming rules, structured PR descriptions, and mandatory work item linking to ensure traceability and consistent collaboration across repositories.

What is the standard format for Git commit messages and pull requests on Azure DevOps?▼

The standard format for Git commit messages and pull requests on Azure DevOps requires consistent naming conventions for commits and branches, alongside structured PR descriptions that include linked work item references.

How do I link Azure DevOps work items to pull requests automatically?▼

Linking Azure DevOps work items to pull requests involves following standardized PR description formats that explicitly require work item association, satisfying traceability requirements for team workflows.

Can I apply existing Git repository conventions to new Azure DevOps projects?▼

You can apply existing Git repository conventions to new Azure DevOps projects by enabling standard branch naming and PR description formats, extending consistent commit and work item linking rules across repositories.

What's the best way to standardize branch naming rules across Flightrac teams?▼

Standardizing branch naming rules across Flightrac teams requires enforcing a shared Git convention that dictates branch formats, commit messaging, and PR guidelines specifically for Azure DevOps repository workflows.

Why do my pull requests fail Azure DevOps work item association checks?▼

Pull requests fail Azure DevOps work item association checks when they do not adhere to established PR conventions, which mandate explicit work item linking and specific PR description formatting for compliance.

Related Skills

Explore More Software Engineering Skills→
shellicarshellicar

hopeventures-conventions

Standardize Git conventions for Hope Ventures on Azure DevOps.

Community
Intermediate
clogacloga
3

git-workflow

Enforce branch-based VCS workflows with pull requests and MCP governance.

Community
Advanced
shellicarshellicar

eagers-conventions

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

Community
Basic
easingthemeseasingthemes
6

dx-pr-commit

Commit code changes and create Azure DevOps pull requests with ADO work items.

Community
Advanced