CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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, fetching, pulling and syncing a branch with its remote, apply, unapply, and linked worktrees. 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 IDs or per-commit file details matter. Replaces git write commands, including fetch and pull. Applies in every checkout of the repository, even when a plain branch is checked out, including linked worktrees such as `.claude/worktrees/*`, and to git writes made while testing or cleaning up (stash, checkout -- <file>, restore, reset).

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

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 strong, dense CLI skill body: fully executable command guidance, clearly sequenced workflows with genuine validation and error-recovery loops, and no wasted explanation of concepts Claude already knows. The main improvement opportunities are consolidating repeated guidance and moving some inline detail into the existing reference files with explicit links.

Suggestions

Consolidate the `--status-after` guidance, which is repeated in ~7 places, into the IDs/Chaining section and reference it once from the recipes.

Link references/concepts.md and references/examples.md directly (e.g., "See [concepts.md](references/concepts.md)") alongside the `but skill concepts` / `but skill examples` commands so the bundle files are discoverable from the body.

Consider moving the long linked-worktree and resolve-conflicts recipe details into a reference file, keeping a condensed core loop in SKILL.md.

DimensionReasoningScore

Conciseness

Assumes Claude's git competence throughout — every rule conveys tool-specific semantics (ID lifetimes, refusal behavior, chaining rules) with no padding or basic-concept explanations. Not 5: the `--status-after` guidance is repeated across roughly seven sections and "but pr new... do not run but push before it" appears twice, so a few instances could be consolidated; not 3: there is no unnecessary explanation beyond that deliberate reinforcement.

4 / 5

Actionability

Fully executable, copy-paste-ready commands with exact syntax throughout: "but commit -b <branch> -m \"<msg>\" <id> <id>", concrete ID examples ("uvw:2e4", "mzm:uvw:2e4"), quoted error strings ("Unclear where to commit. Found more than one stack"), and a fast path for the common selective-commit case. Specific examples cover the common cases comprehensively.

5 / 5

Workflow Clarity

Multi-step recipes are clearly sequenced with explicit validation and feedback loops: the conflict loop ("Go back to step 1 until it reports no conflicts"), `but pull --check` as a preview, `but resolve finish` reporting leftover markers and remaining conflicts, recovery procedures for failed pushes and dependency refusals, and inverse commands for destructive operations. Error recovery is addressed at every fragile step.

5 / 5

Progressive Disclosure

Bundle references (references/concepts.md, references/examples.md) are real, one level deep, and clearly signaled ("For workspace model: `but skill concepts`", "For workflow examples: `but skill examples`"). Not 5: pointers are CLI commands rather than file links, the "but skill reference" pointer has no corresponding bundle file, and the ~250-line body carries dense operational detail inline rather than splitting it into the reference files.

4 / 5

Total

18

/

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.

An excellent description: it enumerates concrete capabilities comprehensively, uses natural trigger vocabulary including git synonyms, and explicitly states both what it does and when to use it. The only weakness is that its most powerful triggers are generic git terms, creating overlap risk with a conventional git skill.

DimensionReasoningScore

Specificity

Lists many concrete actions — "Commit, push, branch... selective dirty-file or hunk commits, branches, diffs, PRs, history edits, squashes, amends, undo, merge, fetching, pulling and syncing... apply, unapply, and linked worktrees" — with comprehensive coverage of the tool's surface. Not 4: that anchor requires minor gaps in coverage, and the enumeration spans the full command surface.

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... Replaces git write commands, including fetch and pull". Concrete trigger phrases are present, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

Comprehensive natural vocabulary users would actually say: "commits", "branches", "diffs", "PRs", "squashes", "amends", "undo", "merge", "fetching", "pulling", "stash", "checkout", "restore", "reset", "worktrees". Includes git synonyms, matching the anchor-5 pattern of synonyms and variations.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (GitButler; "Replaces git write commands, including fetch and pull" scopes the claim), but core triggers like "commit", "push", and "merge" are generic VCS terms that overlap with any plain-git skill, so conflict risk is more than minimal. Not 3: the tool name and replacement framing make it far more distinguishable than a generic "works with document files" description.

4 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.