メニュー
Use when the user wants to view, change, or reset their persistent preferences, or when triggered by "/caliper-settings", "my settings", "change defaults".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | caliper-settings |
| description | Use when the user wants to view, change, or reset their persistent preferences, or when triggered by "/caliper-settings", "my settings", "change defaults". |
View and manage persistent user preferences. Settings follow 3-tier precedence: CLI flag > user setting > shipped default.
Run the settings script to manage preferences:
caliper-settings list
caliper-settings get <key>
caliper-settings set <key> <value>
caliper-settings reset [key]
Shows each setting with its current value (user override or default), the shipped default, and a description.
Returns the merged value (user override if set, otherwise default). Other skills call this as a fallback when no CLI flag is passed.
Persists a user override. The script validates the value against the setting's type (bool, enum, int) and rejects invalid values with a clear error.
Removes a user override so the setting falls back to its shipped default. With no key argument, resets all settings.
| Key | Type | Default | Used by |
|---|---|---|---|
skip_tests | bool | false | pr-create |
review_mode | enum | (prompt) | pr-review |
skip_review | bool | false | pr-review |
merge_strategy | enum | squash | pr-merge |
workflow | enum | (prompt) | design, orchestrate, implement |
planner_model | enum | opus | design |
task_implementer_model | enum | sonnet | orchestrate |
design_reviewer_model | enum | opus | design, design-review |
plan_reviewer_model | enum | sonnet | design, plan-review |
implementation_reviewer_model | enum | opus | orchestrate, implementation-review |
pr_reviewer_model | enum | opus | pr-review |
review_wait_minutes | int | 5 | orchestrate, pr-review |
Other skills check settings as fallbacks when no CLI flag is provided. For example, pr-create checks skip_tests only when --skip-tests wasn't passed. CLI flags always win — settings are tier 2, flags are tier 1.
Use when asked to audit a codebase, find DRY/YAGNI/complexity issues repo-wide, or perform periodic code quality review
Use when a design doc has been written and before draft-plan is dispatched
Use when creating features, building components, adding functionality, or modifying behavior - before any creative or implementation work begins
Use when you have a spec or requirements for a multi-step task, before touching code
Use when implementing a small or medium change directly in the current session, without a multi-task plan — via design's fast-path routing, or direct invocation ("/implement", "just implement this", "quick fix").
Use when a multi-task implementation is complete and ready for holistic review before merging, or asked to review the current branch/diff as a whole