Menú
Build and debug lazygit customCommands in config.yml — prompts, contextual keybindings, commandMenus, template-based construction, and conventional-commit flows. Use when editing lazygit config or designing a custom command.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Browser automation CLI wrapping Playwright for one-shot tasks like navigation, page interaction, screenshots, and scraping. Use when driving a live browser from the terminal. Skip for repeat automations that warrant a full Playwright script.
Author and maintain agent context markdown — AGENTS.md, rules, skills, memory files. Use when creating, editing, or refactoring any agent-focused doc, or after major codebase exploration to capture learning.
Author and audit Agent Skills. Use when creating a new skill, refactoring an existing one, or rewriting skill metadata (name, description, allowed-tools).
Build ASCII/Unicode animations such as loading spinners, logo reveals, particle effects, and terminal art. Covers character grids, frame loops, per-character state machines, ordering, and performance. Use when designing any character-based visual animation.
Run tests, builds, migrations, or any command needing real CI secrets/services on Blacksmith. Use when testing or validating code, or before any commit or push that should be verified against CI.
Use when editing files in a Bun project (bun.lock or bun.lockb at the root, a packageManager field set to bun in package.json, or imports from the bun namespace) or running bun/bunx commands. Covers Bun-native APIs, the bun test runner, bun build --compile, and the Bun-optimized tsconfig.
Basado en la clasificación ocupacional SOC
| name | lazygit-custom-commands |
| description | Build and debug lazygit customCommands in config.yml — prompts, contextual keybindings, commandMenus, template-based construction, and conventional-commit flows. Use when editing lazygit config or designing a custom command. |
context and command are required (except commandMenu entries — see below).
| Field | Notes |
|---|---|
key | Hotkey — omit to expose via ? menu only |
context | Required. Comma-separated for multi: 'commits, subCommits' |
command | Required. Go template string |
description | Shown in UI and ? menu |
loadingText | Progress label while running |
output | none \ |
outputTitle | Title for popup output |
after | checkForConflicts |
prompts | List of prompt configs (see below) |
Keys: single letters or special forms like <c-t>, <f5>, <esc>.
status, files, worktrees, localBranches, remotes, remoteBranches, tags, commits, reflogCommits, subCommits, commitFiles, stash, global
All prompts share: type, title, key. Answers referenced as {{.Form.<Key>}}.
- type: 'input'
key: 'Scope'
title: 'Scope (optional):'
initialValue: ''
suggestions:
preset: 'branches' # authors|branches|files|refs|remotes|remoteBranches|tags
# OR: command: 'my-cmd' (mutually exclusive with preset)
- type: 'confirm'
key: 'Confirm'
title: 'Force-push to remote?'
body: 'This will rewrite history on the remote branch.'
Options: value required, name (display label — shows value if omitted), description, key (direct-select).
- type: 'menu'
key: 'Type'
title: 'Commit type:'
options:
- value: 'feat'
name: 'Feature'
description: 'New functionality'
key: 'f'
- value: 'fix'
key: 'x'
- value: 'chore'
- type: 'menuFromCommand'
key: 'Branch'
title: 'Remote branch:'
command: 'git branch -r --list {{.SelectedRemote.Name}}/*'
filter: '.*{{.SelectedRemote.Name}}/(?P<branch>.*)' # named groups: ?P<name>, unnamed: group_1, group_2...
valueFormat: '{{.branch}}'
labelFormat: '{{.branch | green}}'
Without filter/valueFormat/labelFormat, each output line is both value and label.
Objects available in command and prompts:
SelectedFile (files) · SelectedLocalBranch (localBranches) · SelectedRemote (remotes) · SelectedRemoteBranch (remoteBranches) · SelectedTag (tags) · SelectedCommit (commits) · SelectedCommitRange (commits) · SelectedStashEntry (stash) · SelectedCommitFile (commitFiles) · SelectedWorktree (worktrees) · SelectedPath · CheckedOutBranch (global)
Notable fields: SelectedFile.Name, SelectedFile.HasUnstagedChanges, SelectedRemote.Name, SelectedCommitRange.From/.To.
Helpers: quote (safe shell quoting), runCommand (interpolate single-line command output).
Template example with a conditional:
command: "git {{if .SelectedFile.HasUnstagedChanges}}add{{else}}reset{{end}} {{.SelectedFile.Name | quote}}"
Prefer Go template conditionals (if, else if, eq) over shell parsing complexity.
Groups commands under one top-level key. Only key and description allowed at the top level — full fields go on entries:
customCommands:
- key: 'X'
description: 'Patch workflows'
commandMenu:
- key: 'c'
context: 'commits, subCommits'
description: 'Copy range to clipboard'
command: 'git format-patch --stdout {{.SelectedCommitRange.From}}^..{{.SelectedCommitRange.To}} | pbcopy'
- key: 'v'
context: 'commits'
description: 'Apply from clipboard'
command: 'pbpaste | git am'
global, built-in exists for the active specific context → built-in winsSet output: popup and wrap command in echo to preview template resolution without executing.
Return paste-ready YAML with correct indentation and explicit context. Verify keybinding collisions and .Form.<Key> references before finalizing.
Only fetch these if something specific isn't covered above — the spec is long and will waste a ton of context window tokens if you pull it in wholesale unnecessarily.