Content
92%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A tight, well-sequenced instruction-only workflow with concrete git commands, explicit validation/feedback loops for destructive delivery actions, and clean sectioning. The main gap is actionability—providing a concrete example push/verify command block would make it fully copy-paste ready.
Suggestions
Include a concrete example of the push and post-push verification commands (e.g. git push -u origin <branch> then git rev-parse/@{u}) to reach fully executable guidance.
Optionally inline one short before/after commit-message example pair to make the typed-prefix guidance copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~22-line body is lean and assumes Claude's git competence—no padding, no explanations of what git/pre-commit hooks are—and every line gives actionable guidance, matching the lean/efficient anchor. | 5 / 5 |
Actionability | Concrete commands are given throughout (git status --short --branch, git worktree list --porcelain, git diff --cached --check, typed commit prefixes), but there is no single copy-paste runnable block and a few details (exact push invocation) are left implied. | 4 / 5 |
Workflow Clarity | Clear three-phase sequence (交付前检查 → 暂存与验证 → 交付) with explicit validation checkpoints and a feedback loop (re-check if the pre-commit hook modifies staged content; verify SHA/upstream/remote after push), satisfying the destructive-operation validation requirement. | 5 / 5 |
Progressive Disclosure | A simple, well-sectioned skill with one clearly signaled one-level reference at the top (先读取 ../comet-github/references/maintainer-contract.md) and no nested indirection, meeting the simple-skill exception for a top score. | 5 / 5 |
Total | 19 / 20 Passed |