CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-backport

Back-port a specific commit from master to a release branch via cherry-pick. Creates a dedicated backport branch, attempts the cherry-pick, pushes it, and opens a PR by default. Returns to the original branch when done (success or failure). If there are merge conflicts, diagnoses the root cause without attempting an autonomous resolution. Use when asked to "backport", "cherry-pick to release", or "port a fix to a release branch".

Quality

90%

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

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

A highly actionable, well-sequenced workflow: every step has executable commands, validation checkpoints appear before risky operations, and failure paths (patch conflict, gh auth) are handled explicitly rather than left implicit. The main costs are repetition between the steps and the 'Important rules' section and the length of the single-file body.

Suggestions

State the 'return to ORIGINAL_BRANCH before stopping' rule once (e.g., in the Important rules section) instead of repeating it at each early-exit point, and reference it from the steps.

Deduplicate the 'Important rules' section against the step bodies, keeping it to genuinely cross-cutting rules only (never checkout -- file, never apply versioning files, never auto-resolve conflicts).

Consider moving the verbatim commit-message and PR-body templates into a short reference file to slim the main body, since they are pasted verbatim rather than reasoned about.

DimensionReasoningScore

Conciseness

Nearly every sentence carries skill-specific operational detail (branch naming convention, versioning-file exclusion, the prohibition on 'git checkout <sha> -- <file>'), with no explanation of concepts Claude already knows. Not 5: the 'Checkout ORIGINAL_BRANCH before stopping' clause repeats about five times and the 'Important rules' section restates rules already given in the steps; not 3: the redundancy is deliberate emphasis, not unnecessary explanation.

4 / 5

Actionability

Every step ships copy-paste-ready commands with clearly marked placeholders: 'git rev-parse --verify <COMMIT_SHA>^{commit}', 'git show ... | git apply --index', the full commit-message template, the PR body template, and 'gh pr create' with all flags, plus a concrete fallback path when gh auth fails. Not 4: there are no gaps — both success and failure paths are fully executable.

5 / 5

Workflow Clarity

Steps 0-7 are clearly sequenced with explicit validation checkpoints (SHA resolution, remote ref existence, clean working tree, branch-already-exists check), error-recovery branches (apply failure → Step 7 diagnosis; gh auth failure → manual PR URL), a human-in-the-loop checkpoint (6a pause for versioning), and a closing rules checklist. Not 4: validation is explicit and comprehensive rather than having minor gaps.

5 / 5

Progressive Disclosure

Well-organized single-file structure (Steps 0-7 with lettered subsections, a diagnosis table, a closing rules section) with no dead references, which is appropriate for a linear single-procedure skill with no bundle files. Not 5: at ~330 lines it exceeds the under-50-line simple-skill case, and the inlined commit-message/PR-body templates plus duplicated rules content could be split or deduplicated; not 3: navigation is easy and nothing that clearly belongs in a separate file is buried.

4 / 5

Total

18

/

20

Passed

Description

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

An excellent description: third-person voice, comprehensive concrete actions covering the full workflow including conflict and cleanup behavior, and an explicit 'Use when...' clause with natural trigger phrases. The only room for improvement is broader synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

"Creates a dedicated backport branch, attempts the cherry-pick, pushes it, and opens a PR by default... diagnoses the root cause without attempting an autonomous resolution" lists multiple concrete actions covering the entire workflow end-to-end. Not 4: coverage is comprehensive (setup, apply, conflict path, push, PR, cleanup) rather than having minor gaps.

5 / 5

Completeness

Clearly answers both questions: the 'what' is concrete (cherry-pick a commit to a release branch, create branch, push, open PR, return to original branch, diagnose conflicts) and the 'when' is an explicit "Use when asked to" clause with concrete trigger phrases. Not 4: the 'when' is fully explicit rather than merely present.

5 / 5

Trigger Term Quality

The explicit trigger clause "Use when asked to 'backport', 'cherry-pick to release', or 'port a fix to a release branch'" uses exactly the natural phrasings a user would say. Not 5: only single forms of each term appear, missing common variations such as 'backport a PR', 'apply a fix to the release', or the hyphenated 'back-port' in trigger position; not 3: coverage is good, not partial.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche — back-porting a commit from master to a release branch via cherry-pick — with distinct trigger phrases unlikely to fire for other git skills. Not 4: overlap risk with generic commit/PR skills is minimal, not 'minor'.

5 / 5

Total

19

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

coinbase/cds

Path

.claude/skills/git-backport/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.