CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autofix

Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.qwen/skills/autofix/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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.

An exceptionally actionable, rigorously sequenced operational skill whose workflows leave nothing ambiguous — every command, schema, threshold, and stop condition is spelled out. Its weaknesses are the opposite trade-off: a ~680-line monolithic body with repeated command lists, duplicated bilingual rules, and over-detailed gate internals, and no use of reference files to split the four modes' detail out of the top-level SKILL.md.

Suggestions

State the trusted verification command list once in GitHub Actions Rules and reference it from develop-issue and address-review ("run the trusted checks per GitHub Actions Rules") instead of repeating the full build/typecheck/lint/Vitest/bundle/schema list three times.

Split each mode's detail (address-review's gate rules, the in-round self-review procedure) into per-mode reference files under references/ loaded when the Invocation block names the mode, keeping SKILL.md a lean routing overview with a short summary of each mode.

Consolidate the two bilingual-output rule blocks into one section covering both the PR-comment files (with the details block) and failure.zh.md (plain Markdown, no HTML), and trim gate-internal mechanics (test-skip spellings, byte-truncation behavior) to the decision-relevant rule.

DimensionReasoningScore

Conciseness

The ~680-line body is noticeably verbose: the trusted verification-command list (build/typecheck/lint/focused Vitest/bundle/generate:settings-schema) is repeated verbatim in three places, the bilingual-output rules are explained in two long overlapping blocks, and external gate internals (every .skip spelling, byte-truncation mechanics) are over-explained. It avoids anchor 1 only because nothing teaches concepts Claude already knows — it is dense operational content with systemic redundancy rather than pedagogical padding.

2 / 5

Actionability

Guidance is fully executable throughout: exact shell commands (the env -u SANDBOX review run invocation, the self-review CLI command), exact JSON output schemas (decision.json, self-review.json, comment-replies.json, test-weakening.json, deferred-findings.json, growth-audit.json), exact git expressions, and precise numeric thresholds (150 lines, 75 minutes, ~8 findings per round). This matches the anchor-5 example of copy-paste-ready commands covering the common cases.

5 / 5

Workflow Clarity

Every mode is a numbered, explicitly sequenced procedure with fail-closed validation checkpoints (entry/exit fingerprints, terminal-status field checks, event classification), feedback loops (fix-and-rerun failing checks, serial review rounds with progress tests), explicit stop conditions (NO_CHANGES/CONVERGED/BLOCKED/STALLED), and exhaustive checklists. This is a clear anchor-5 match; anchor 4 would imply missing checkpoints, and none are missing.

5 / 5

Progressive Disclosure

The body has real, navigable structure (per-mode ## headers, ### subsections, fenced command and JSON blocks), so it is above anchor 2's "minimal structure". But no references/ or assets/ bundle files exist and everything — including the ~350-line address-review section with its gate rules and the in-round self-review subsection — is inlined in one monolithic SKILL.md, fitting anchor 3's "content that should be separate is inline".

3 / 5

Total

15

/

20

Passed

Description

58%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.

A concrete, reasonably specific description that clearly states what the skill does across its local and CI modes, with a distinct branded identity. Its main weaknesses are the complete absence of any "Use when" trigger guidance and thin synonym coverage, which limit discoverability and cap completeness and trigger-term quality.

Suggestions

Add an explicit "Use when..." clause naming the triggering situations, e.g. "Use when the user asks to autofix, fix, or repair local changes, or to fix a CI failure or address review feedback on an issue or PR."

Include natural trigger synonyms beyond "Autofix" and "repair" — "fix", "CI failure", "PR review feedback", "address review comments" — so users' phrasing matches the description.

Briefly state what the issue and review workflows do (e.g. "...workflows, which implement issue fixes and address PR review feedback") to close the specificity gap.

DimensionReasoningScore

Specificity

"Review and repair current local changes until they converge" plus "run Qwen Code Autofix issue and review workflows from GitHub Actions" lists several concrete actions (review, repair, run two named workflows). It falls short of anchor 5 because what the issue and review workflows actually do (fix issues, address PR feedback) is never stated.

4 / 5

Completeness

The "what" is clear (review/repair local changes to convergence; run the two GitHub Actions workflows), but there is no "Use when..." clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not score 2, because the "what" half is concrete and specific rather than vague.

3 / 5

Trigger Term Quality

Relevant terms are present ("review", "repair", "local changes", "Autofix", "issue", "GitHub Actions") but common variations users would naturally say are missing: "fix", "PR"/"pull request", "CI failure", "review feedback". It matches anchor 3 (some relevant keywords, missing synonyms) rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

"Qwen Code Autofix" and "GitHub Actions" pin a distinct branded niche, but the opening clause "Review and repair current local changes" overlaps generic code-review and fix-changes skills. Anchor 4 (mostly distinct, minor overlap with closely related skills) fits; anchor 5 would require fully distinct triggers.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (688 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

QwenLM/qwen-code

Path

.qwen/skills/autofix/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.