Menu
Build and troubleshoot lazygit customCommands in config.yml. Use for prompt-driven commands, context-specific keybindings, commandMenus, template-based construction, and conventional-commit style workflows.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Manage Obsidian vault frontmatter with rematter — validate schemas, sync to external destinations (Astro, etc.) with media options, rename fields, manage filenames. Load whenever performing bulk operations in Obsidian vaults (or other collections of markdown with frontmatter).
Use when asked to automate an action for OpenCode, for example run a formatter after edits, or running a script right before git commits, those are hooks and you should use this skill to implement them.
Guide the learner through a structured goal-setting exercise grounded in research on Mental Contrasting with Implementation Intentions (MCII). The exercise helps developers set concrete learning goals, visualize meaningful outcomes, anticipate realistic obstacles, and build if-then plans to overcome them.
Facilitates deliberate skill development during AI-assisted coding. Offers interactive learning exercises after architectural work (new files, schema changes, refactors). Use when completing features, making design decisions, or when user asks to understand code better. Supports the user's stated goal of understanding design choices as learning opportunities.
Generates a repo-specific orientation.md resource for the learning-opportunities skill. Only invoke via slash command (/orient:orient). Do not trigger automatically.
Use when asked to add or modify hooks for Claude Code specifically. Or, if the user is asking to automate an action, for example run a formatter after edits, or running a script right before git commits, those are hooks and you should use this skill to implement them.
| name | lazygit-custom-commands |
| description | Build and troubleshoot lazygit customCommands in config.yml. Use for prompt-driven commands, context-specific keybindings, commandMenus, template-based construction, and conventional-commit style workflows. |
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 | terminal | log | logWithPty | popup |
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.