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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

77%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 exceptionally actionable and validation-heavy, with exact commands, JSON contracts, and fail-closed outcomes for every mode, giving it top workflow clarity. Its weaknesses are length-driven: a 683-line monolith that repeats the trusted-check and bilingual rules multiple times and keeps mode-specific detail inline instead of splitting it into reference files.

Suggestions

Split each mode (local working tree, assess-candidates, develop-issue, address-review) into its own reference file under references/, keeping SKILL.md as a routing overview with the shared Rules for Every Mode.

Factor the trusted verification command list (npm run build/typecheck/lint, focused Vitest, bundle integration, generate:settings-schema) into a single stated-once section instead of repeating it verbatim in GitHub Actions Rules, develop-issue step 6, and the address-review finish block.

Trim dated fleet statistics and repeated justifications (e.g. the takeover-fleet self-review numbers and the twice-stated bilingual translation rules) to the operative rule plus a one-line rationale.

DimensionReasoningScore

Conciseness

Every rule is domain-specific operational policy rather than known-concept padding, but the 683-line body repeats material: the trusted-check command list appears verbatim three times (GitHub Actions Rules, develop-issue step 6, address-review finish), the bilingual-output rule is stated twice, and self-review fleet statistics ("measured on the takeover fleet (40 PRs, 2026-09-10)") pad the rationale. This fits the mostly-efficient-but-could-be-tightened anchor 3, not anchor 2 since no section explains things Claude already knows.

3 / 5

Actionability

The guidance is fully executable: exact shell commands ("env -u SANDBOX QWEN_SANDBOX=true \"${QWEN_CODE_CLI:-qwen}\" review run --approval-mode auto --effort high --json --quiet"), exact JSON output shapes for decision.json, self-review.json, comment-replies.json and test-weakening.json, exact git expressions, file paths, and terminal statuses. It matches the copy-paste-ready anchor 5.

5 / 5

Workflow Clarity

Each mode has a numbered sequence with pervasive explicit validation checkpoints (entry/exit content fingerprints, an exhaustive list of fail-closed completion conditions, mutation probes before commit) and genuine feedback loops (fix-and-rerun while an evidence-backed hypothesis remains, iterate review rounds until convergence with STALLED/BLOCKED/CONVERGED outcomes). This is the clear-sequence-with-validation-and-recovery-loop anchor 5.

5 / 5

Progressive Disclosure

The body has real section structure (per-mode headers, a shared GitHub Actions Rules section) so it is not the minimal-structure anchor 2, but it is a single 683-line monolith where per-mode detail (address-review alone spans ~380 lines), bilingual-output rules, and gate-parsing rules clearly belong in separate reference files; the only referenced files (.qwen/skills/*, AGENTS.md) are external to the bundle, and the bundled scripts/run-agent.mjs is never referenced. This matches the some-structure-but-should-be-split anchor 3.

3 / 5

Total

16

/

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 states concrete, distinctive capabilities in third person with decent natural keywords, but it lacks any explicit "Use when..." trigger guidance, capping completeness. Adding a trigger clause and common synonyms ("fix", "CI", "working tree") would raise it.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to fix, repair, or review local changes, or when a Qwen Code Autofix GitHub Actions workflow invokes the skill."

Include common user synonyms such as "fix", "working tree", and "CI" alongside "repair" and "local changes" to broaden natural keyword coverage.

Distinguish the local mode from ordinary code-review requests more sharply (e.g. "iterates review-and-fix rounds until the tree converges") to reduce overlap with generic review skills.

DimensionReasoningScore

Specificity

Names several concrete actions — "Review and repair current local changes until they converge", "run Qwen Code Autofix issue and review workflows from GitHub Actions" — matching the anchor listing several specific actions with minor gaps, but not the comprehensive multi-action coverage of a 5.

4 / 5

Completeness

The "what" is clear (review/repair local changes to convergence, run Autofix issue and review workflows), but there is no "Use when..." clause or equivalent explicit trigger guidance, which the judging guidelines cap at 3.

3 / 5

Trigger Term Quality

Natural terms like "review", "repair", "local changes", "converge", "GitHub Actions", and "Autofix" give good keyword coverage, though common synonyms users would say ("fix my changes", "working tree", "CI") are missing, so it fits anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Distinctive markers ("Qwen Code Autofix", "GitHub Actions", "converge") establish a niche, but "Review and repair current local changes" overlaps generic code-review and fix skills, matching the mostly-distinct anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

15

/

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 (684 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.