skills.rest
videojs
videojsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

git

Enforce Git workflow conventions for Video.js 10 commits, branches, and PRs.

888|82|Updated Aug 13, 2025
Search Tags:#git#workflow#commit#branch#pull-request#conventional-commits#branch-naming
One-click install
npx skills add https://github.com/videojs/v10 --skill git-videojs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git
Source: https://github.com/videojs/v10/tree/main/.claude/skills/git
Command: npx skills add https://github.com/videojs/v10 --skill git-videojs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill standardizes and enforces Git workflow conventions for Video.js 10, ensuring consistent commit messages, PR descriptions, and branch naming across all contributions.

Core Features & Use Cases

  • Conventional commits: Enforces commit messages that follow the conventional format to improve history readability and traceability.
  • Branch naming: Provides guidelines for feature/bugfix branch naming to simplify review and tracking.
  • PR discipline: Standardizes PR titles and descriptions to improve coordination and review quality.
  • Scope inference: Uses path-based scope mapping to infer component areas from changes and guide reviews.
  • Examples: When contributing to core, create a feature branch like feat/login, commit as feat(auth): add login support, and open a PR with a standardized template.

Quick Start

Create a feature branch using the recommended naming, commit changes with a conventional message, push, and open a PR with a consistent description.

Frequently Asked Questions about git

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

FAQPage Schema
How do I format conventional commits for Video.js 10 contributions?▼

Conventional commits for Video.js 10 require a specific format to ensure traceability, such as structuring messages like feat(auth): add login support to maintain readable history across core library and ecosystem components.

What is the standard branch naming convention for Video.js 10 feature branches?▼

The branch naming convention for Video.js 10 simplifies review and tracking by using path-based guidelines, recommending formats like feat/login for feature branches and specific naming for bugfixes to guide reviews.

How do I structure a pull request description for Video.js 10?▼

Pull request descriptions for Video.js 10 must follow a standardized template to improve coordination and review quality, enforcing consistent PR titles and descriptions that align with the documented workflow conventions.

Can I use path-based scope mapping to infer component areas in Video.js 10?▼

Path-based scope mapping infers component areas from your changes to guide reviews in Video.js 10, automatically determining the affected scope for both core library and ecosystem components during commits and PRs.

When do I need to apply Git workflow conventions for Video.js 10?▼

Git workflow conventions apply whenever you are contributing to the Video.js 10 repository, specifically guiding authors through commits, branch creation, and pull requests for both core library and ecosystem components.

Related Skills

Explore More Software Engineering Skills→
dwmkerrdwmkerr
23

my-repos

Locate dwmkerr's repositories locally or clone them from GitHub.

Community
Intermediate
MayaDispelerMayaDispeler
3

git-workflow

Enforce git commit message formats, branch naming, and pull request guidelines.

Community
Advanced
LimaTechnologiesLimaTechnologies

git-workflow

Guide Git workflows with branch naming, conventional commits, and pre-commit hooks.

Community
Basic
jaeyeonlingjaeyeonling

git-workflow

Standardize Git workflows with conventional commits and branching strategies.

Community
Intermediate