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.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/version-control/SKILL.md

Quality

Content

76%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 dense, highly actionable command reference that concentrates on genuine depot_tools/Gerrit knowledge Claude would not otherwise have. Its weak spot is the absence of validation checkpoints in the destructive/batch workflows (archiving, stack uploads, rebasing), which caps workflow clarity, along with some repetition across the emphasis callout, body, and Common Mistakes sections.

Suggestions

Add validation checkpoints to the destructive/batch flows, e.g. 'after git reparent-branch --root, verify git cl status shows the new parent and no conflicts before git cl archive -f', and 'confirm the stack is clean after git rebase-update before uploading'.

Consolidate the triple repetition of key rules (IMPORTANT block, inline sections, Common Mistakes) — keep the callout and one canonical section, and let the Quick Reference table carry the rest.

Consider moving the long Detaching-from-landed-CLs procedure and the Release/Roll Status lookup into separate reference files to keep SKILL.md as a leaner overview.

Dimension	Reasoning	Score
Conciseness	Lean and imperative throughout, spending tokens only on non-obvious project facts (why 'git new-branch' is required, why 'gclient sync -Df' must follow 'git rebase-update'); the main trimmable redundancy is that key rules appear up to three times (IMPORTANT block, body sections, Common Mistakes) — anchor 4's minor trims rather than anchor 3's noticeable verbosity.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover every common case: 'git new-branch <branch-name>', 'git cl upload -f -d --commit-description="<description>"', 'git reparent-branch --root', 'git rebase-update && gclient sync -Df', plus the concrete Chromium Dash API URL.	5 / 5
Workflow Clarity	Sequences are clear and ordering caveats are explicit ('run git fetch ... before archiving', 'run reparent before archiving'), but the destructive/batch workflows (force-archiving branches with 'git cl archive -f', force-uploading entire stacks, rebasing stacks) have no validation checkpoints or verify-then-proceed steps — the rubric's batch/destructive cap applies despite the good sequencing.	3 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers, a Quick Reference table, and no nested references; at ~105 lines with some inline bulk (e.g. the Release and Roll Status lookup and the long Detaching paragraph) it fits anchor 4's 'good structure, minor organization gaps' rather than anchor 5's fully split, easy-navigation layout.	4 / 5
	Total	16 / 20 Passed

Description

75%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 description with an explicit, comprehensive trigger list and a clearly staked-out niche in the DevTools Gerrit workflow. Its main weakness is that the 'what' — what the skill actually does or provides — is only implied by the directive to avoid standard git commands.

Suggestions

State the 'what' explicitly before the trigger clause, e.g. 'Provides depot_tools/Gerrit commands for branch, CL, and stack management in Chrome DevTools.'

Add the natural synonyms users may say — 'change list', 'amend', 'rebase', 'sync dependencies', 'depot_tools' — to improve trigger coverage.

Tighten the broad 'starting a new task' trigger (e.g. 'starting a new task in the DevTools repo') to reduce false activation on unrelated tasks.

Dimension	Reasoning	Score
Specificity	Names the domain and lists several concrete actions ("creating a branch", "creating and uploading CLs", "handling stacked changes", "checking release and roll status"), but actions are phrased as trigger conditions rather than capability statements and coverage has gaps (amending, reparenting, syncing) — below anchor 5's comprehensiveness, above anchor 3's 1-2 actions.	4 / 5
Completeness	The 'when' is explicit and detailed ("Use when starting a new task, creating a branch, ... in the DevTools Gerrit-based workflow"), and a 'what' is implied by "ALWAYS use this instead of running standard git checkout/switch commands for branch creation", but the 'what' is never explicitly stated — better than anchor 3's missing 'when', short of anchor 5's explicit what AND when.	4 / 5
Trigger Term Quality	Good natural keyword coverage ("starting a new task", "creating a branch", "switching branches", "stacked changes", "release and roll status", "uploading CLs"), but missing common synonyms and variations ("change list", "amend", "rebase", "sync", "depot_tools") — fits anchor 4 rather than anchor 5's comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	Clear niche via "DevTools Gerrit-based workflow", "CLs", and "roll status"; minor overlap risk remains with generic git/version-control skills through "creating a branch, switching branches" and the broad "starting a new task" trigger — anchor 4, not anchor 5's minimal conflict risk.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ChromeDevTools/devtools-frontend
Path: .agents/skills/version-control/SKILL.md
Commit: de3f9ca

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

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.