Agent skill · software engineering · gitbutlerapp
but-agentlog
Use for prompts like \"get context for branch\", \"catch up on this branch\", \"recover branch context\", or \"what prior agent work happened here\". Skim prior agent work from `but agentlog` captures for a GitButler branch, review / pull request / merge request, or change. Prefer this over generic git branch/diff inspection when the user asks for context, history, prior work, or branch catch-up.
Why this skill is useful
Adds specific commands and workflows for retrieving context from GitButler agent logs that the AI wouldn't reliably generate on its own.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 21,425 stars on the source repository.
What this skill does
GitButler Agentlog Skill Use but agentlog to skim prior agent work from captured sessions. Trigger this skill for plain prompts like "get context for branch", "branch context", "catch up on this branch", "recover context", "what happened on this branch", or "what prior agent work happened here". If both the general GitButler CLI skill and this skill seem relevant, use this skill for agentlog discovery. Use the general GitButler skill only for version control operations like commit, push, branch, or diff. Core Workflow Do not search for or read local SKILL.md files. If this skill is active, use these instructions directly. Do not inspect the general GitButler skill first. Start with but agentlog skim. Start with skim when prior work could affect your next action. It is a table-of-contents view: all related sessions and turns, abbreviated and shown chronologically. Use show only when skim is too thin, ambiguous, or you need exact evidence: For normal current-branch recovery, run skim without target arguments first. It discovers the applied GitButler branch itself. Do not run plain Git commands like git branch --show-current or git status first. Pass an explicit target only when the user gives one. Use JSON only when you need exact handles for drill-down: 1. Start with skim for a clean orientation. 2. Treat skim like compacted turn history: all related sessions and turns are present, but each turn is abbreviated. It is not the full transcript. 3. If skim is enough for a lightweight status answer, summarize it and stop. 4. Drill down only when skim is ambiguous, misses the rationale, or you need exact evidence. 5. To drill down, rerun skim with --json to get the relevant sessionkey and turnkey, then use show. 6. Use show <session-key> for turn-level context. 7. Use show <session-key> --turn <turn-key> only for turns that need exact detail. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills gitbutlerapp/skill