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

94%

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

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 dense, highly actionable CLI skill body with concrete commands, well-sequenced workflows, and explicit validation/feedback loops for risky operations. Its main weakness is mild redundancy of commit syntax across sections and some inline command-reference detail that mirrors references/reference.md.

Suggestions

Consolidate the recurring `but commit -b <branch> -m ... <ids>` syntax into one canonical statement and reference it from 'Start Here' and 'Task Recipes' rather than re-stating it.

Move the 'Command Patterns' bulleted flag reference into references/reference.md, keeping SKILL.md focused on the quick-start path and task recipes.

Tighten the 'IDs' section's chaining paragraph, which currently interleaves several rules that could be split into a short table or sub-bullets for faster scanning.

Dimension	Reasoning	Score
Conciseness	Mostly lean and Claude-competence-assuming with concrete commands, but the `but commit -b <branch> -m ... <ids>` syntax recurs across 'Start Here', 'Command Patterns', and 'Task Recipes', adding some redundancy that could be tightened.	4 / 5
Actionability	Copy-paste-ready bash with exact flags, ID forms, and chained `&&` patterns throughout, e.g. 'but commit -b <branch> -m "<msg>" <id> <id>' and 'but uncommit <source-commit-id> && but diff', covering common cases exhaustively.	5 / 5
Workflow Clarity	Multi-step recipes (pull, split, reorder, conflict resolution) are explicitly sequenced with validation feedback loops — 'Go back to step 1 until it reports no conflicts', 'but resolve finish reports leftover markers... When it says no conflicted commits remain, stop' — exactly the destructive/batch safety the rubric rewards.	5 / 5
Progressive Disclosure	Clear one-level-deep references to reference.md/concepts.md/examples.md, all verified to exist and signaled in the Notes section, but the inline 'Command Patterns' and 'Git-to-But Map' overlap with reference.md's command reference, a minor organization gap.	4 / 5
	Total	18 / 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.

A strong, third-person description that concisely states capabilities, gives explicit 'Use for...' trigger guidance with natural terms, and distinguishes the skill from plain git. It also surfaces diagnostic command-selection hints without padding.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'commit, push, branch... 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...'), with concrete trigger phrases and even diagnostic guidance ('use `but status -fv` when file/hunk IDs... matter').	5 / 5
Trigger Term Quality	'Use for commits, selective dirty-file or hunk commits, branches, diffs, PRs, history edits, squashes, amends, undo' are exactly the natural phrases users say, with good synonym coverage; file extensions are not applicable for a CLI tool.	5 / 5
Distinctiveness Conflict Risk	Pinned specifically to GitButler (`but`) and closes with 'Replaces git write commands', carving a clear niche with distinct triggers and minimal overlap with generic git skills.	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: 5546418

Reviewed: about 4 hours 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.