メニュー
Use fzf for interactive fuzzy selection from files, branches, and command output. Trigger when a human-in-the-loop selection step is needed inside terminal workflows.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | tool-fzf |
| description | Use fzf for interactive fuzzy selection from files, branches, and command output. Trigger when a human-in-the-loop selection step is needed inside terminal workflows. |
fzf
git branch --all | fzf
fd -t f | fzf
fzf --preview 'bat --color=always {}'
printf '%s\n' foo bar baz | fzf --filter 'ba'
fzf --multi
--filter when running without an interactive TTY.130 indicates cancel, not regular no-results.--multi emits newline-separated selections and needs downstream handling.FZF_DEFAULT_COMMAND can change behavior.--filter prints matches non-interactively and returns 0/1.Drive a unit of work through the basicly harness loop end-to-end (intake → classify → decompose → build → verify → ship → teardown → retro) using `basicly loop` + `br`, agent-agnostic across Claude/Codex/Copilot. Use when starting or resuming non-trivial development in a harness-enabled repo, when deciding what phase a tracked issue is in, or when coordinating the checkpoints, gates, and bounded rework the loop enforces.
Use br (beads_rust) as the primary task/issue tracker for this repo. Trigger when planning work, creating or claiming issues, checking what is ready to work on, or preparing a commit that must reference a beads issue id.
Use Node and npm in this repo for the markdownlint git hook and other node tooling. Use when running npm or npx committing or pushing from a script or background job on WSL or debugging a node-based hook that resolves the wrong node binary.
Write and edit Python for this repo — type hints pathlib and cross-platform subprocess and shell-out. Use when creating or changing .py files wiring up a subprocess call or chasing a test that passes on POSIX but fails only on Windows CI (a WinError 2 or a mangled backslash path).
Write isolated order-independent automated tests that assert on observable behavior rather than private internals. Use when writing reviewing or debugging any test (unit integration or end-to-end) in any language especially when tests share fixtures touch global or filesystem state flake depending on run order or reach into implementation details.
Close out a working session with a usage-statistics report, a self-improvement retro, and a pickup-clean handoff summary. Use when the user says the session is done ("wrap up", "finish the session", "close out"), before ending a long autonomous run, or whenever a summary of what changed and what the agent actually used is wanted.