Automated summary
This skill enforces Video.js 10 Git workflow conventions for commit messages, branch names, and pull request descriptions.
Strengths
- Formats commits as `type(scope): description` with scope inference
- Automates the branch → commit → push → PR sequence through the `/commit-pr` command
- Ships dedicated references for commits, scope, PRs, and branch naming
Limitations
- Conventions are specific to Video.js 10 and need adaptation for other repositories
- Does not cover conflict resolution, rebase, or history rewriting
- Relies on loading the `references/` files for detailed guidance
Use it when creating a branch, writing a conventional commit, or opening a pull request in the Video.js 10 repository.
Avoid it on projects with different Git conventions, or for advanced Git operations such as conflict resolution or interactive rebase.
Security analysis
SafeThis skill is purely documentation of Git workflow conventions. It contains no executable commands, tool invocations, network access, secret handling, or destructive instructions, so the listing risk is negligible.
No concerns found
How this analysis is madeExamples
Commit my staged changes with a conventional commit message for Video.js 10.Push my current branch and open a pull request with a proper description.What should I name the branch for adding a new caption renderer?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
- Create branch following naming convention
- Make changes
- Commit with conventional message
- Push and create PR with proper description
For the /commit-pr command, all steps after branching are automated.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/git-workflow-conventions-for-video-js-10-mm5t899k/download' --output '.skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k/SKILL.md.part' && mv '.skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k/SKILL.md.part' '.skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Quick Reference
Commit: type(scope): lowercase description
Branch: type/short-description
PR Title: Same as commit (or RFC: / Discovery: prefix)
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k/SKILL.md' && test -s '.skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/git' && cp -R '.skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k' '.claude/skills/git'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k'openskills read 'git-workflow-conventions-for-video-js-10-mm5t899k'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/git-workflow-conventions-for-video-js-10-mm5t899k/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.