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

93%

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

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A concise, highly actionable skill body with clear sequenced workflows and a useful quick-reference table. Its main gap is the absence of validation/feedback checkpoints for batch operations like git rebase-update and the consequential upload step.

Suggestions

Add a validation checkpoint after git rebase-update (e.g., check for rebase conflicts per branch and how to resolve/abort) since it rebases all branches at once.

Add a verify step after git cl upload (e.g., confirm the new patch set appears on the Gerrit CL URL) to close the loop on the consequential upload operation.

Note how to handle amend conflicts or failed uploads so the workflow has an explicit feedback loop rather than only the happy path.

Dimension	Reasoning	Score
Conciseness	Command-focused and lean; the brief overview ('one branch per CL ... you amend your single commit locally') conveys project-specific context Claude would not already know rather than restating generic git concepts, fitting the 'lean and efficient' anchor.	3 / 3
Actionability	Provides fully executable commands (git new-branch, git commit --amend, git cl upload -f -d, git reparent-branch, git rebase-update) plus a copy-paste Quick Reference table, matching the 'fully executable ... copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Creating → Making Changes → Amending → Upload), but git rebase-update is a batch operation across all branches and git cl upload is consequential, with no validation checkpoints or conflict-resolution feedback loops — so it is capped at 2 per the batch-operations guideline rather than reaching the explicit-validation level 3.	2 / 3
Progressive Disclosure	Self-contained skill with no bundle files; sections are well-organized (Overview, Core Workflow, Quick Reference, Common Mistakes) with no nested references or monolithic wall of text, satisfying the well-organized self-contained case rather than the could-be-better-organized level 2.	3 / 3
	Total	11 / 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, specific description with explicit triggers, concrete enumerated capabilities, and a clearly delineated niche that distinguishes it from standard git skills. It answers both what and when without padding.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions — 'creating a branch, switching branches, managing branches, creating and uploading CLs, handling stacked changes, or checking release and roll status' — matching the 'lists multiple specific concrete actions' anchor rather than the domain-only level 2.	3 / 3
Completeness	Explicit 'Use when ...' trigger answers 'when', and the enumerated actions plus 'DevTools Gerrit-based workflow' domain answer 'what', satisfying the both-what-and-when anchor; it is not level 2 because the trigger guidance is explicit rather than implied.	3 / 3
Trigger Term Quality	Covers natural terms a user would say ('creating a branch', 'switching branches', 'CLs', 'stacked changes', 'release and roll status') with good variation, fitting the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped to 'DevTools Gerrit-based workflow' with an explicit 'ALWAYS use this instead of running standard git checkout/switch commands' directive, giving it a clear niche unlikely to conflict with generic git skills.	3 / 3
	Total	12 / 12 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: 184a74d

Reviewed: 3 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.