Git 版本控制与协作专家,涵盖 GitHub/Gitee 平台操作、Conventional Commits 规范及 PR/MR 最佳实践。
53
27%
Does it follow best practices?
Impact
98%
1.12xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/05-devops-gitworkflow/SKILL.mdConventional commit message format and type usage
Format: type(scope): desc
80%
80%
feat type used
100%
100%
fix type used
100%
100%
docs type used
100%
100%
perf or refactor type used
100%
100%
test type used
100%
100%
Scope present in all messages
80%
80%
Only approved types
100%
100%
Lowercase description
100%
100%
Trunk-based development branching strategy
TBD recommended
0%
100%
main is always releasable
100%
100%
Feature branches are short-lived
58%
100%
Feature branches deleted after merge
100%
100%
Correct main branch name
100%
100%
repo-setup.sh creates main branch
100%
100%
Script is executable and commented
100%
100%
Worked example included
100%
100%
No Git Flow as primary
0%
100%
GitHub Actions CI/CD and Pages setup
Uses GitHub Actions for CI
100%
100%
CI triggers on push and PR
100%
100%
CI runs tests
100%
100%
CI runs linter
100%
100%
Release workflow uses GitHub Actions
100%
100%
Release triggers on version tags
100%
100%
NPM publish step present
100%
100%
GitHub Pages for docs hosting
100%
100%
package.json has required scripts
100%
100%
Workflows under .github/workflows/
100%
100%
3dd3ac0
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.