but

Commit, push, branch, and manage version control with GitButler. Use for commits, selective dirty-file or hunk commits, branches, diffs, PRs, history edits, squashes, amends, undo, merge, apply, and unapply. For selected dirty files or hunks, inspect with `but diff`; use compact `but status` for commit order, branch/stack placement, or conflict overview; use `but status -fv` when file/hunk IDs or per-commit file details matter. Replaces git write commands.

Quality

91%

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

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

The body is a highly actionable, command-dense reference that avoids explaining concepts Claude already knows and supplies sequenced recipes with recovery loops. Its main weaknesses are mild cross-section repetition and verification guidance that is mostly conditional rather than mandatory.

Suggestions

Consolidate the repeated commit fast path and diff/status selection guidance into one authoritative section, then reference it from elsewhere to trim redundancy.

Promote the 'but skill reference/concepts/examples' pointers inline near the relevant sections (e.g., command patterns, recipes) instead of only in the closing Notes, so detailed material is discoverable where it is needed.

For destructive operations like 'but discard', state an explicit verification step (e.g., run 'but diff' or 'but status' first to confirm the targeted IDs) rather than leaving validation implicit.

Dimension	Reasoning	Score
Conciseness	Dense and command-focused throughout, with no padding about basic git concepts, but the commit fast path and the diff/status guidance recur across 'Start Here', 'Command Patterns', and the recipes — minor repetition that could be tightened.	4 / 5
Actionability	Fully executable, copy-paste-ready commands cover the common cases — 'but commit -b <branch> -m "<msg>" <id> <id>', 'but push <top-branch>', 'but pr new <branch-name>' — with concrete IDs and flag combinations throughout.	5 / 5
Workflow Clarity	Recipes are clearly numbered and sequenced with the conflict-resolution recipe providing an explicit feedback loop and 'but undo' recovery, but much of the verification guidance is conditional ('add --status-after only when...') rather than mandatory explicit checkpoints.	4 / 5
Progressive Disclosure	SKILL.md is an overview with the bulk split into references/concepts.md, examples.md, and reference.md, signaled one level deep via 'but skill reference/concepts/examples' — good structure, though the pointers live in a Notes section rather than inline near each topic and are CLI commands rather than direct links.	4 / 5
	Total	17 / 20 Passed

Description

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

The description is specific, trigger-rich, and complete, naming a comprehensive set of concrete version-control actions and explicit 'Use for' triggers tied to the GitButler CLI. It clearly distinguishes itself from generic git skills.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'commits, selective dirty-file or hunk commits, branches, diffs, PRs, history edits, squashes, amends, undo, merge, apply, and unapply' — giving comprehensive coverage of the tool's capabilities.	5 / 5
Completeness	Explicitly answers both what ('Commit, push, branch, and manage version control with GitButler') and when ('Use for commits, selective dirty-file or hunk commits...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers the natural terms users say for version control — commit, push, branch, diff, PR, squash, amend, undo, merge — plus variations like 'selective dirty-file or hunk commits'.	5 / 5
Distinctiveness Conflict Risk	Has a clear niche (GitButler CLI) and the explicit 'Replaces git write commands' marker makes conflict with generic git skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gitbutlerapp/gitbutler
Path: crates/but/skill/SKILL.md
Commit: e64149e

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