skills.rest
Integra-Beauty
Integra-BeautyOFFICIAL
Explore all skills by this author →
GitHub

integra-git-conventions

Enforce kebab-case branch names, conventional commits, and repository naming conventions.

Updated Aug 23, 2026
Search Tags:#git#workflow#branching#commits#naming#conventional-commits
One-click install
npx skills add https://github.com/Integra-Beauty/integra-conventions --skill integra-git-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: integra-git-conventions
Source: https://github.com/Integra-Beauty/integra-conventions/tree/main/skills/integra-git-conventions
Command: npx skills add https://github.com/Integra-Beauty/integra-conventions --skill integra-git-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inconsistent git workflows hamper collaboration. This skill codifies Integra's git conventions for branches, commits, and repository naming to ensure uniform practices across teams.

Core Features & Use Cases

  • Branch naming rules: kebab-case, lowercase, no secrets or noise in names.
  • Commit messages: follow Conventional Commits loosely; focus on one concern per commit; aim for small, revertible commits.
  • Repo naming and synchronization: keep project and repository names in sync across tooling and resources.
  • Use cases: onboarding new contributors and maintaining a tidy git history across long-running projects.

Quick Start

Name your next branch in kebab-case and write a small, single-scope commit using a conventional-commits style.

Frequently Asked Questions about integra-git-conventions

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

FAQPage Schema
What is the best way to enforce consistent git branch naming conventions across a team?▼

Consistent git branch naming is achieved by applying lowercase kebab-case formatting without secrets or noise, ensuring uniform practices and readable history across software development teams.

How do I write conventional commit messages for small, single-scope changes?▼

Conventional commit messages should follow a loosely structured format focusing on one concern per commit, aiming for small, easily revertible commits that keep the git history tidy and maintainable.

Do I need to keep my repository name synchronized with my project name in git workflows?▼

Yes, repository naming synchronization requires keeping the project and repository names in sync across tooling and resources, which prevents ambiguity and maintains consistency across long-running projects.

How does one-concern-per-commit workflow improve git history?▼

A one-concern-per-commit workflow improves git history by enforcing commit scope discipline, ensuring each commit addresses a single issue, which makes changes easier to track, review, and revert when necessary.

Can I use conventional commits and kebab-case branches for onboarding new contributors?▼

Yes, conventional commits and kebab-case branch naming are ideal for onboarding new contributors because they codify clear git conventions, reducing workflow inconsistency and helping new team members adopt uniform practices quickly.

Related Skills

Explore More Software Engineering Skills→
pradeepmoulipradeepmouli
2

speckit-git-initialize

Initialize a Git repository with configurable branch and .gitignore settings.

Community
Intermediate
genesis-agentsgenesis-agents
2

Git Workflow

Implement Git workflow conventions and CI checks for GenesisPod projects.

Community
Intermediate
VYRE-StudiosVYRE-Studios

commit-push-pr

Commit staged changes, push the branch, and open a pull request via GitHub CLI.

Official
Intermediate
masermediagroup-stackmasermediagroup-stack
1

managing-git-workflows

Configure Git workflows with branching strategies, conventional commits, and hooks.

Community
Advanced