CtrlK
BlogDocsLog inGet started
Tessl Logo

github-fix-issue

Fix GitHub issues end-to-end — analysis, branch creation, implementation, testing, and PR submission. Use whenever the user mentions fixing a GitHub issue, says "fix issue

79

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, well-sequenced end-to-end workflow with concrete gh/git commands, a test validation checkpoint, and a substantive untrusted-content security note. It is self-contained and appropriately organized with no unnecessary nested references.

DimensionReasoningScore

Conciseness

The body is lean and mostly bullet-pointed with executable commands, assuming Claude's competence rather than explaining basic concepts (no 'what a PR is' padding); the few motivational one-liners are brief and orienting rather than verbose.

3 / 3

Actionability

It provides fully executable, copy-paste-ready commands in the gh Command Reference and inline (e.g. 'gh issue view <number>', 'gh pr create --title ... --body "Fixes #123"'), matching the anchor for specific executable examples.

3 / 3

Workflow Clarity

A clearly numbered six-step sequence is present with an explicit validation/feedback checkpoint in the Test step ('Fix any failing tests before moving on'), and a 'ask clarifying questions before proceeding' gate in step 1.

3 / 3

Progressive Disclosure

This is a self-contained single-purpose skill with no bundle files and no external references; its well-organized sections (numbered workflow subsections plus a command reference) satisfy the simple-skill allowance for scoring 3.

3 / 3

Total

12

/

12

Passed

Description

100%

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 strong, third-person description that clearly states concrete end-to-end capabilities and pairs them with explicit, natural-language trigger phrases including multilingual variants. It fully answers both what the skill does and when to invoke it.

DimensionReasoningScore

Specificity

The description lists multiple concrete end-to-end actions — 'analysis, branch creation, implementation, testing, and PR submission' — matching the anchor for listing several specific concrete actions, not merely naming a domain.

3 / 3

Completeness

It explicitly answers both 'what' (Fix GitHub issues end-to-end with the listed phases) and 'when' via an explicit 'Use whenever the user mentions...' trigger clause, so it is not capped at 2.

3 / 3

Trigger Term Quality

It surfaces natural phrases a user would actually say — 'fix issue #123', 'work on this issue', '修复 issue', and 'references a GitHub issue number or URL' — giving good coverage rather than only technical jargon.

3 / 3

Distinctiveness Conflict Risk

The GitHub-issue-fixing niche with distinctive triggers ('fix issue #123', GitHub issue URL) is unlikely to fire for unrelated skills; it is more specific than the score-2 'could still overlap' anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
feiskyer/claude-code-settings
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.