ワンクリックで
redaction-logs
Manage logging, redaction, and output formats safely. Use when the user asks about logs, secrets, or JSON output.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Manage logging, redaction, and output formats safely. Use when the user asks about logs, secrets, or JSON output.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Author Sitecore recipes (.recipe.ts) that compile to templates + renderings — map a React/SXA component to a component-template, model data with content-templates, define enums, group with component-sections. Use when creating or editing *.recipe.ts files, turning a component into a Sitecore rendering, or asking "how do I make a recipe / why doesn't my component show up in Pages".
Non-negotiable codebase conventions for the scai CLI — module boundaries, error contract, credential handling, agent contract, quality gates. Trigger when writing or modifying code in scai.
Project-specific testing patterns for scai — Vitest tiers, mocking conventions, integration gating, and where tests live. Trigger when writing tests, debugging test failures, or asking about how to test something.
Navigate scai's access model — the workspace policy allowlist and the credential/keychain patterns. Use when a command fails with POLICY_DENIED or AUTH_REQUIRED, when authenticating an environment, or to pick the fastest route to gain access to an environment.
Reference card for working on the scai CLI locally — boot sequence, common commands, env setup, sandbox tenant, and gotchas. Read this at the start of a session that involves running, building, or testing scai.
Run the CLI safely in non-interactive or CI environments. Use when the user mentions agents, CI, non-TTY, automation, or headless runs.
| name | redaction-logs |
| description | Manage logging, redaction, and output formats safely. Use when the user asks about logs, secrets, or JSON output. |
--json for machine parsing--quiet to suppress non-error output--log-file <path> to capture full logs--trace for detailed HTTP/debug logging--log-file for post-run analysis.