et-git

ET git workflow for preparing commits and reviewing changes. Use when checking git status or diff, filtering unrelated files, staging task-scoped changes, writing Chinese commit messages, or synchronizing with remotes using rebase instead of merge.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-structured overview with concrete commands and a clear workflow that includes validation checkpoints, deferring detail to a single well-signaled reference. Adding an inline commit-message example and explicit feedback-loop language would push it to full marks.

Suggestions

Include one concrete Chinese commit-message example inline (e.g. '优化 ET skills 路由与参考文档') so the '动作 + 对象 + 影响范围/原因' format is immediately actionable.

Make the validate→fix→retry loop explicit in the body for risky operations (e.g. 'rebase 冲突 → 解决 → git rebase --continue → 再次检查 staged diff') rather than relying on the reference file.

The '优先入口' command list duplicates commands already implied by '默认动作'; consider merging to tighten token use further.

Dimension	Reasoning	Score
Conciseness	Lean, sectioned body that assumes Claude's git competence — '红线：禁止直接使用 git pull', short bullet steps — with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Concrete commands are listed verbatim ('git status --short', 'git diff --staged', 'git pull --rebase') and the 6-step default action sequence is actionable, but no inline commit-message example is shown in the body.	4 / 5
Workflow Clarity	A clear numbered sequence with an explicit re-check checkpoint (step 4 re-examines staged diff before commit) and a risk-explain-before-execute checkpoint (step 6); validation is present so the destructive/batch cap does not apply, though explicit validate→fix→retry feedback loops are only weakly emphasized in the body.	4 / 5
Progressive Disclosure	Under 50 lines with well-organized sections and a single, clearly signaled one-level reference ('references/et-git-workflow.md' under '按需补读') whose file exists in the bundle.	5 / 5
	Total	18 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinct, clearly stating both capabilities and trigger conditions in third person. Trigger-term coverage is strong though a few natural synonyms are missing.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'preparing commits', 'checking git status or diff', 'filtering unrelated files', 'staging task-scoped changes', 'writing Chinese commit messages', 'synchronizing with remotes using rebase instead of merge' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers 'what' ('ET git workflow for preparing commits and reviewing changes') and 'when' ('Use when checking git status or diff...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural phrases users would say ('git status or diff', 'staging task-scoped changes', 'commit messages', 'synchronizing with remotes') are well covered, but a few common synonyms (amend, stash, branch) are absent.	4 / 5
Distinctiveness Conflict Risk	The ET-specific niche, Chinese commit messages, and rebase-not-merge constraint give it clear distinct triggers with minimal conflict risk against generic git skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: egametang/ET
Path: Packages/cn.etetet.harness/skills/et-git/SKILL.md
Commit: ff68102

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.