git Pass

Git workflow conventions for Video.js 10. Commit messages, PR descriptions, branch naming, and scope inference. Triggers: "commit", "push", "create PR", "conventional commit", "branch name", "open pull request".

64out of 100
851
stars
17
downloads
105
views

// Install Skill

Install Skill

Skills are third-party code from public GitHub repositories. SkillHub scans for known malicious patterns but cannot guarantee safety. Review the source code before installing.

Install globally (user-level):

npx skillhub install videojs/v10/git

Install in current project:

npx skillhub install videojs/v10/git --project

skill.install.customTargetHelp

npx skillhub install videojs/v10/git --target-dir /path/to/skills

Suggested path: ~/.claude/skills/git/

AI Review

64
out of 100
Instruction Quality70
Description Precision72
Usefulness47
Technical Soundness75

Scored 64 as a solid contributing skill with well-organized reference files and progressive disclosure. Strong description with 6 triggers. Limited by project-specific scope (Video.js 10 only) and lack of automation scripts or error handling. Valuable as part of a Contributing to Video.js bundle.

betasimplevideojs-contributorsopen-source-contributorsgit-workflowconventional-commitspr-creationbranch-namingscope-inference
Reviewed by reviewer-service(ocg/glm-5.1) on 8/23/2026

SKILL.md Content

---
name: git
description: >-
  Git workflow conventions for Video.js 10. Commit messages, PR descriptions,
  branch naming, and scope inference. Triggers: "commit", "push", "create PR",
  "conventional commit", "branch name", "open pull request".
context: fork
---

# Git

Git workflow conventions for Video.js 10.

## Reference Material

| Task                  | Load                   |
| --------------------- | ---------------------- |
| Writing commits       | `references/commit.md` |
| Inferring scope       | `references/scope.md`  |
| Creating/updating PRs | `references/pr.md`     |
| Naming branches       | `references/branch.md` |

## Quick Reference

**Commit:** `type(scope): lowercase description`

**Branch:** `type/short-description`

**PR Title:** Same as commit (or `RFC:` / `Discovery:` prefix)

## Process

1. Create branch following naming convention
2. Make changes
3. Commit with conventional message
4. Push and create PR with proper description

For the `/commit-pr` command, all steps after branching are automated.

License

No license was declared in this skill's source.

The full license text is available in the source repository.

View the license in the source repositorythe version published there is authoritative.