Agent Skills
› videojs/video.js
› commit-pr
commit-pr
GitHub自动化执行代码提交、推送及创建或更新 Pull Request 的流程。确保变更符合规范，智能选择范围，构建完整 PR 描述并报告结果，适用于需要发布或准备合并请求的场景。
触发场景
用户明确要求提交代码并推送
用户要求创建或更新 Pull Request
安装
npx skills add videojs/video.js --skill commit-pr -g -y
SKILL.md
Frontmatter
{
"name": "commit-pr",
"description": "Commit, push, and create or update a Video.js pull request. Use when the user explicitly requests repository publication or PR preparation."
}
Commit and pull request
Preserve unrelated user changes. Do not stage or rewrite files you cannot attribute to the requested work.
Workflow
- Inspect
git status, staged and unstaged diffs, branch name, and commits since the merge base. - Read the relevant reference only when needed:
- Commit wording:
references/commit.md - Scope selection:
references/scope.md - Branch naming:
references/branch.md - PR title/body:
references/pr.md - Evidence for observable skin or site visual changes:
references/visual-evidence.md
- Commit wording:
- Split changes into semantic commits when they represent independently reviewable purposes. Never use
git add .; stage explicit paths or a reviewed set. - Run the checks appropriate to each commit before committing.
- Use a conventional commit accepted by
commitlint.config.js; treat that config and recent history as the current source of truth. - Push only when requested. Check for an existing PR before creating one.
- Build the PR description from the complete branch diff, not only the last commit. Explain motivation, behavior, verification, and relevant issue links. For observable changes to skin or site visual elements, choose proportional evidence using
references/visual-evidence.md. - Report commit hashes, checks, and the PR URL.
Do not amend, force-push, change an existing PR title, or update an existing PR body without clear user authorization.
Example
Input: “Commit these skill changes and open a draft PR.”
Output: Intentionally scoped commits, recorded checks, a pushed branch, and the draft PR URL.
版本历史
- 8a0a3d8 当前 2026-10-20 08:02
