ossrules.md

but

Contributors

GitHub-linked commit authors for this SKILL.md at the saved revision. Co-authors and history before file renames are not included. Some commit authors have no linked GitHub account.

File history ↗

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.

crates/but/skill/SKILL.md

Partial bundle · download unavailable
master · 1f5041d ↗8 bundle filesScanned 2026-09-14

AGENTS.md

560 tokens · o200k_base · 2,255 bytes

SourceGitHub ↗

Editing the bundled but skill

SKILL.md and references/ are installed verbatim into users' agents — a wrong line here misdirects every agent in every user repo. Only the files in SKILL_FILES in crates/but/src/command/skill/mod.rs ship, so register any new reference file there. stub.md is the body of the single-file stub install. It points only at but skill commands and says what each prints and how to read it; command syntax and behavior stay in the served guide, where they cannot go stale.

  • Never document anything that can block on a TTY. An editor or interactive picker hangs an agent forever. Give the non-interactive form (-m, --no-message, -F, -t, --yes), and where the blocking variant is one omitted argument away — bare but push — name it and warn against it rather than staying silent.
  • Never document what you have not observed. Help text and doc comments state intent and drift from behavior, so build the CLI and run the command against a scratch repo — setting E2E_TEST_APP_DATA_DIR to a temp dir keeps it off your real GitButler data. Sample output in examples is a claim too. Warnings need the same evidence: if you cannot reproduce the failure one prevents, cut it.
  • Never document commands agents should not run: subcommands and flags marked hide = true in crates/but/src/args/ (the hidden flags on push are the usual trap), and the TUI/GUI surfaces.
  • Never mention --format json or other output formats. Agents read the default agent output; format-specific notes (flags, streams, JSON shapes) don't belong in skill files.
  • When a command changes, re-derive its guidance instead of syntax-swapping the prose; rationale written for the old implementation dies with it. The same facts are deliberately repeated across the four installed files — grep and update every occurrence.
  • Leave version: 0.0.0 alone. inject_version string-replaces that exact text at install time, so "fixing" it silently breaks skill versioning.
  • Keep the frontmatter description under 1024 characters. Past that, Codex drops it outright and Claude Code truncates it — the skill loses its trigger text with no error either way.
← All GitButler skillsProject instructions →