skills.rest
Inteligentsensingsolutions
InteligentsensingsolutionsOFFICIAL
Explore all skills by this author →
GitHub

dev-conventions

Standardize branch naming, commit formats, labels, and PR conventions for Git workflows.

1|Updated Apr 13, 2026
Search Tags:#code-review#pull-requests#git-workflow#branch-naming#commit-messages#dev-conventions
One-click install
npx skills add https://github.com/Inteligentsensingsolutions/tdd-dev-workflow --skill dev-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-conventions
Source: https://github.com/Inteligentsensingsolutions/tdd-dev-workflow/tree/main/skills/dev-conventions
Command: npx skills add https://github.com/Inteligentsensingsolutions/tdd-dev-workflow --skill dev-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a centralized guide for branch naming, commit messaging, PR naming, and merge policies to harmonize development practices across teams.

Core Features & Use Cases

  • Standardizes branch naming and commit conventions to improve readability and traceability.
  • Defines PR naming, label usage, and protected-branch rules to accelerate reviews and releases.
  • Use case: onboarding new teammates with a clear, single source of truth for development workflows.

Quick Start

Review and publish your team's branch naming, commit message, and PR conventions in a single, accessible guide.

Frequently Asked Questions about dev-conventions

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

FAQPage Schema
What are standard branch naming and commit message conventions for a Git workflow?▼

Standard Git workflow conventions enforce structured branch naming schemes and conventional commit formats to improve readability, traceability, and consistency across software teams during feature development and code reviews.

How do I establish pull request naming and label usage rules for my development team?▼

You establish pull request naming and label usage rules by defining standardized PR conventions and protected-branch policies, creating a centralized guide that accelerates code reviews and release management across the team.

Can I use these development conventions for onboarding new teammates to our Git workflow?▼

Yes, you can use these development conventions for onboarding new teammates by providing a clear, single source of truth for branch naming, commit messaging, and merge policies to harmonize their development practices quickly.

What is the best way to standardize merge policies and protected branches for release management?▼

The best way to standardize merge policies and protected branches is to publish a centralized guide defining PR naming, label usage, and protected-branch rules to ensure consistency and accelerate releases.

Do I need specific Git workflow tools to enforce conventional commit formats and branch naming schemes?▼

You do not need specific external tools to establish these conventions, as the focus is on defining and publishing standardized branch naming, commit formats, and PR rules to harmonize development practices manually across software teams.

Related Skills

Explore More Software Engineering Skills→
alslimanyalslimany

spatie-version-control

Apply Spatie Git conventions to commits, branches, PRs, and naming.

Community
Intermediate
dtsongdtsong
1

GitHub PR Update

Update a pull request branch with latest base branch changes via merge or rebase.

Community
Intermediate
jamestorrevillasjamestorrevillas
3

git-workflow

Standardizes Git commits, PRs, and branching with Conventional Commits and templates.

Community
Intermediate
vanman2024vanman2024
3

Git Workflows

Standardize git workflows with commit templates, branch helpers, and hook scripts.

Community
Basic