CtrlK
BlogDocsLog inGet started
Tessl Logo

devtools-version-control

Use when starting a new task, creating a branch, switching branches, managing branches, creating and uploading CLs, handling stacked changes, or checking release and roll status in the DevTools Gerrit-based workflow. ALWAYS use this instead of running standard git checkout/switch commands for branch creation.

76

Quality

95%

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

93%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 efficient, highly actionable command reference with good sequencing and a useful common-mistakes section. The only gap is the absence of explicit validation/feedback loops for the destructive upload and rebase operations.

Suggestions

Add an explicit verification step after 'git cl upload' (e.g., confirm the CL URL or check Gerrit status) to close the validation loop on this non-interactive upload.

For 'git rebase-update' and 'git reparent-branch', add a brief post-command check (e.g., 'git cl status' or confirm branch parent) so errors surface before further work.

Add a short note on what to do when an upload or rebase fails (re-amend and re-upload) to give a concrete recovery path.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: every line is a concrete command or a direct rule, with no padding or explanation of concepts Claude already knows (e.g., what git or Gerrit is).

5 / 5

Actionability

Fully executable, copy-paste-ready commands cover every common case (new-branch, amend, stacked CLs, reparent, rebase-update, upload), reinforced by a quick-reference table.

5 / 5

Workflow Clarity

Clear numbered sequences for making changes and amending, plus a common-mistakes checklist, but upload/rebase operations lack explicit validate→fix→retry checkpoints, leaving minor validation gaps.

4 / 5

Progressive Disclosure

A compact, well-organized skill under 50 lines with clear section headers and no bundle files; the simple-skill exception applies and structure is easy to navigate.

5 / 5

Total

19

/

20

Passed

Description

96%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 strong, specific description that clearly states both capability and trigger conditions with natural phrasing. The DevTools/Gerrit scoping keeps it largely distinct from generic git skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'starting a new task, creating a branch, switching branches, managing branches, creating and uploading CLs, handling stacked changes, or checking release and roll status' — with comprehensive coverage of the workflow.

5 / 5

Completeness

Explicitly answers both 'what' (DevTools Gerrit-based branch/CL/release workflow) and 'when' via the 'Use when ...' clause enumerating concrete triggers.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases users would actually say: 'creating a branch', 'switching branches', 'uploading CLs', 'stacked changes', 'release and roll status'.

5 / 5

Distinctiveness Conflict Risk

The 'DevTools Gerrit-based workflow' framing carves a clear niche, though branch creation is a general git concept with minor overlap risk against a generic git skill.

4 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ChromeDevTools/devtools-frontend
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.