CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pre-push-check

Run the full pre-push review pipeline — code review checks, self-review against CLAUDE.md, and a final report.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 well-structured, highly actionable pre-push workflow with copy-paste commands, explicit validation checkpoints, fallback chains, and a concrete report template. Its only weakness is minor redundancy between the step 3 and step 4 checklists.

DimensionReasoningScore

Conciseness

The body is efficient — concrete commands, a tight checklist, and a functional report template with no explanations of concepts Claude already knows — but step 4's items (console.log, error handling) overlap step 3's checklist and could be trimmed, matching the minor-instances anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands ('git diff --stat', 'git log --oneline origin/HEAD..HEAD', 'devflow check'), an explicit fallback chain (Claude Code → OpenCode → 'yarn lint'/'yarn build'), specific checklist items, and a complete report template. Per the scoring notes, an instruction-only skill needs actionable guidance rather than code, which this fully satisfies.

5 / 5

Workflow Clarity

A clear six-step sequence with explicit validation checkpoints (devflow check with fallback chain, CLAUDE.md compliance pass, common-issues pass), a PASS/WARN/FAIL verdict gate, and a feedback loop in step 6 (list issues → ask user → push only when clean) — matching the anchor with explicit validation steps and error-recovery paths.

5 / 5

Progressive Disclosure

No bundle files exist and nothing in the body references any, so nothing is buried or nested; all content (checklist, report template) appropriately lives in the single well-sectioned file with easy navigation, which per the simple-skill scoring note earns full marks.

5 / 5

Total

19

/

20

Passed

Description

66%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 clearly states what the skill does with several named pipeline components, but entirely lacks an explicit 'Use when...' trigger clause, leaving the activation conditions only weakly implied. Trigger keyword coverage is good though missing common variations, and it is mostly distinct from related review skills.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user is about to push, asks for a pre-push check, or wants changes reviewed before pushing.'

Include natural trigger variations such as 'before push', 'push check', or 'quality gate' alongside 'pre-push' to broaden keyword coverage.

Name the concrete tooling behind 'code review checks' (e.g., devflow check with lint/type-check fallback) to sharpen the specificity of the what.

DimensionReasoningScore

Specificity

Names the domain ('pre-push review pipeline') and lists three concrete actions ('code review checks', 'self-review against CLAUDE.md', 'and a final report'), matching the anchor for several specific actions with minor gaps — 'code review checks' is generic and the underlying tooling is unnamed.

4 / 5

Completeness

The 'what' is clear (runs code review checks, CLAUDE.md self-review, and a final report), but there is no 'Use when...' clause or equivalent — the 'when' is only weakly implied by 'pre-push', which caps this dimension at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('pre-push', 'code review', 'self-review', 'CLAUDE.md') that users would plausibly say, but common variations like 'before push', 'push check', or 'quality check' are missing, so it falls short of comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The pre-push pipeline framing and CLAUDE.md self-review form a mostly distinct niche, though 'code review checks' creates minor overlap risk with generic code-review skills — matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

AndreJorgeLopes/devflow

Path

skills/pre-push-check/SKILL.md

Reviewed

Table of Contents

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.