メニュー
Use ripgrep for extremely fast text and regex search across repositories. Trigger when locating symbols, strings, or patterns at scale.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | tool-ripgrep |
| description | Use ripgrep for extremely fast text and regex search across repositories. Trigger when locating symbols, strings, or patterns at scale. |
rg "pattern" path/
rg -F "exact string"
rg "pattern" -t py
rg "pattern" -g '*.py'
rg "pattern" -C 3
rg -l "pattern"
rg -c "pattern"
rg -i "pattern"
rg "pattern" --json
rg --exit-status "pattern"
-n when actionable line references are needed.-F for literal strings to avoid regex escaping mistakes.--glob/-g and type filters to keep results relevant and fast.--json emits begin/match/end/summary events, not a single flat schema.path:line:column:matched_text.--exit-status is useful in conditional shell pipelines.rg --json produces structured, machine-parseable search events.--user-install is referenced."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.