메뉴
Quick reference for backtick tools, levels, and configuration.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | backtick-help |
| description | Quick reference for backtick tools, levels, and configuration. |
| license | MIT |
Answer with this reference, trimmed to what was asked.
| Level | Behavior |
|---|---|
| lite | Full answer plus a one-line TL;DR on top |
| full | The cut enforced: answer-first, no filler (default) |
| ultra | Minimum viable answer; challenges wrong questions |
| off | backtick inactive |
| Command | What it does |
|---|---|
/backtick [lite|full|ultra|off] | Set the level; no argument reports the current one |
/backtick default <lite|full|ultra|off> | Persist the default for new sessions |
/backtick-review | Cut-list for the current diff |
/backtick-audit | Repo-wide cut hunt |
/backtick-debt | Harvest backtick: omission markers |
/backtick-gain | Benchmark scoreboard (only from real results) |
/backtick-help | This reference |
Codex invokes skills with @ (@backtick-review); Copilot CLI namespaces
them (/backtick:backtick-review).
Default level resolution, first match wins:
BACKTICK_DEFAULT_MODE env var (lite/full/ultra/off)defaultMode in ~/.config/backtick/config.json (%APPDATA%\backtick\config.json on Windows)fullDeactivate for the session: "stop backtick" or "normal mode".
Scope subagent injection with the BACKTICK_SUBAGENT_MATCHER env var
(regex tested against the subagent type; unset = inject everywhere).
One-shot: answer and stop. Do not switch modes or persist state.
Local task compiler: prepare_task before exploring, work from the evidence packet, verify_patch before done.
Local task compiler for repository coding work. Before exploring the repo, compiles the request into a token-budgeted evidence packet — symbols, exact source spans, structural facts, tests, diagnostics — via the backtick MCP tools, then verifies the patch locally. Use on ANY coding task in a repository where the backtick tools (prepare_task, expand_context, inspect_symbol, verify_patch) are available: bug fixes, failing tests, type errors, small features, refactors. Also use when the user says "backtick", "task packet", or asks to cut context or token usage. Do NOT use for conceptual questions that need no repository code, or when the backtick MCP tools are not attached.
Benchmark scoreboard for backtick, real results only, never invented numbers.
Shows the measured impact scoreboard for backtick from the benchmark results in this repo. Use when the user says "backtick gain", "what does backtick save", or asks for the numbers. One-shot: do NOT change the active backtick mode or persist anything.
Quick reference for the backtick commands, levels, and configuration. Use when the user says "backtick help", asks what backtick commands exist, how to change the level, or how to turn backtick off. One-shot: do NOT change the active backtick mode or persist anything.