Results for “settings”

Use when preparing for a Salesforce seasonal release — triaging release notes, reviewing Release Updates, opting into Sandbox Preview, and communicating change impact to stakeholders. Triggers: 'upcoming Salesforce release', 'release notes triage', 'Release Updates', 'sandbox preview opt-in', 'release readiness checklist', 'production upgrade date', 'feature impact', 'critical update', 'roll out the Spring release safely', 'is our org ready for the Spring release', 'release update settings metadata', 'FlowSettings release update field', 'release run sheet', 'preview sandbox refresh freeze', 'settings deploy flipped a release update'. Also covers: which Release Updates are deployable as Settings metadata, the release run sheet artefact, and the preview opt-in refresh-date rule. NOT for planning your own release train — use devops/release-management. NOT for user training and go-live comms — use admin/change-management-and-training.

The English summary is being prepared. Showing the original description.

Configuring Salesforce lead management and conversion in Setup: lead settings, web-to-lead, conversion field mapping, lead queues, auto-response rules, lead processes. Trigger keywords: web-to-lead, lead conversion, lead field mapping, lead settings, lead process, lead queue, lead auto-response. NOT for Apex that controls what conversion creates - use apex/lead-conversion-customization. NOT for lead assignment rule logic - use admin/assignment-rules. NOT for duplicate rule configuration - use admin/duplicate-management. Also covers: LeadConvertSettings objectMapping XML, LeadConfigSettings, LeadStatus StandardValueSet converted flag, lead process BusinessProcess, Database.convertLead bulk conversion limits.

The English summary is being prepared. Showing the original description.

Use when admins are reducing Chatter signal-to-noise across an org — covers org-level Chatter Email Settings, per-user Email Settings preferences, group-level email digest frequency (Daily / Weekly / Every post / Never), bell-icon Custom Notifications vs Chatter feed-post tradeoffs, automated-feed suppression on record types via Feed Tracking config, and the Chatter Settings org defaults that control whether new users start with everything-on. Triggers: 'chatter feed full of automated posts nobody reads', 'users complain about chatter email volume', 'turn off chatter notifications for a specific group', 'change default chatter digest frequency', 'stop process builder posts from filling the feed', 'NotificationFrequency invalid value', 'ChatterEmailsMD.settings will not deploy', 'custom notification recipient limit'. NOT for Custom Notifications API design (use apex/apex-custom-notifications-from-apex), NOT for Connect API / Chatter REST API integration patterns (use apex/apex-connect-api-chatter), NOT for Chatter group lifecycle, archiving, ownership and unlisted-group governance (use admin/chatter-group-governance).

The English summary is being prepared. Showing the original description.

Use when configuring or troubleshooting Salesforce CPQ contract creation, subscription management, amendment quotes, or renewal quotes. Trigger keywords: contract, amendment, renewal, subscription, co-termination, SBQQ__Subscription__c. NOT for designing the amendment/renewal architecture or swap pattern — use architect/subscription-management-architecture. NOT for amending or renewing contracts from Apex — use apex/cpq-api-and-automation. Also covers the standard Contract and Order objects underneath CPQ — Contract Status vs StatusCode, activation locking, EndDate auto-calculation, ContractSettings and OrderSettings, reduction orders, and renewal-reminder automation. Trigger keywords: Contract, ContractStatus, StatusCode, ActivatedDate, OwnerExpirationNotice, ContractTerm, EndDate, Order, OrderItem, reduction order, ContractSettings, OrderSettings, renewal reminder. NOT for Revenue Cloud or Subscription Management objects — use architect/revenue-cloud-architecture and architect/subscription-management-architecture.

The English summary is being prepared. Showing the original description.

Wire up GSettings: schema authoring, key naming, settings binding to widgets, window state persistence. Use when persisting app settings or window size/state in a GNOME app.

The English summary is being prepared. Showing the original description.

Reads and changes a running CARLA server's WorldSettings via apply_settings — synchronous vs asynchronous mode, fixed_delta_seconds (fps), physics substepping, and no_rendering_mode — and keeps the Traffic Manager's sync state matched automatically. Use when the user asks to "enable/disable sync mode", "set synchronous mode", "run at a fixed fps/step", "turn off rendering", "make the sim deterministic", or "restore async mode", and as the prerequisite for keeping settings across a map load.

The English summary is being prepared. Showing the original description.

Claude Code (code.claude.com) の CLI 本体リファレンス。 CLAUDE.md memory, settings.json (All settings, settings precedence, managed-settings.json), env-vars, model config, keybindings, statusline, terminal config, cli-reference (-p / --continue / --resume), sessions, checkpointing, worktrees, remote control, channels, deep links, troubleshooting。

The English summary is being prepared. Showing the original description.

新しいフックの雛形（スクリプト + 配線）を本リポジトリの規約どおりに生成する。 イベント選定（PreToolUse / PostToolUse / Stop / SessionStart 等）とブロッキング可否を対話的に決め、 ai-agents/hooks/ か ai-agents/settings/<cli>/hooks/ への配置と、hooks.json / settings.json への配線まで行う。 新しいフックを追加したいときに `/hook-scaffold <フック名> [用途の一言]` で呼び出す。

The English summary is being prepared. Showing the original description.

直近の Claude Code 会話ログを分析し、CLAUDE.md / .claude/skills / .claude/rules / .claude/settings* の改善案を提案・適用するレトロスペクティブスキル。ユーザーが「retro して」「振り返りして」「最近の会話から CLAUDE.md (や skills, rules, settings) を改善して」「繰り返し指摘していることをルール化して」など、過去のやり取りをもとに設定・スキルを改善する意図を示したら必ず使用する。

The English summary is being prepared. Showing the original description.

Audit-and-fix method for one user setting area across every repo. Use when a setting seems ignored, duplicated or confusing, on 'audit the X settings' or 'why doesn't my X setting apply', or as a lane of the settings sweep. NOT for adding a new setting (use build-sub-feature).

The English summary is being prepared. Showing the original description.

Set up Claude Code hooks that block Git commands such as push, hard reset, and forced deletion before execution. Choose project-wide or global settings, customize the blocked commands, and verify that the hook rejects a test command.

• Block Git pushes from Claude Code
• Prevent commands that discard changes or delete branches
• Apply Git restrictions to one project or all projects

Audit Claude Code configuration with AgentShield to find exposed secrets, excessive permissions, unsafe hooks, and prompt injection risks, where malicious instructions influence an agent. Generate reports, apply supported automatic fixes, or create a security-focused starter configuration.

• Checking configuration when starting a Claude Code project
• Auditing permission and MCP configuration changes
• Reviewing existing configuration in a newly joined repository

Review Django authentication, permissions, input handling, and production settings. Use concrete configuration and code examples to address malicious queries, unwanted requests, injected scripts, unsafe uploads, and API access, alongside secret management and security logging.

• Reviewing login and user permissions
• Checking production security settings before deployment
• Reviewing input handling and request protection

Track machine learning experiments in W&B, record training settings and metrics, and compare results in dashboards. Automate searches for training settings and keep version histories for models and datasets.

• Comparing accuracy across training runs
• Monitoring training progress in dashboards
• Searching for better training settings

Configure deployment, the process of publishing an application, for /land-and-deploy. Identify the hosting platform, production URL, health check endpoints, and status commands, then save those settings in CLAUDE.md for future deployments.

• Preparing settings for /land-and-deploy
• Identifying the hosting platform and production URL
• Saving health checks and deployment status commands

Find guidance on Codex settings, pricing, and OpenAI products and APIs using current official documentation. Get cited answers for setup, troubleshooting, model comparisons, migration planning, and prompt changes, with uncertainty stated when sources are inconclusive.

• Check Codex settings and troubleshoot problems
• Compare models for cost, speed, and quality
• Plan a model migration and adjust prompts

Prepare and submit requests to add agents in Paperclip. Check hiring permissions, compare existing configurations, and define the role, instructions, reporting line, and runtime settings, then handle approval and follow-up for linked tasks.

• Requesting a new agent for a specific role
• Matching a new agent to existing team settings
• Drafting role instructions and runtime settings

Verify WorldMonitor dashboard behavior using existing browser tests or focused manual interactions. Check panels, map layers, settings, search, and country briefs, while collecting screenshots, logs, and persisted-state evidence to document the results.

• Checking dashboard startup after a change
• Verifying panel settings and saved layouts
• Testing map layers, search, and country briefs

Manage OmniRoute context settings from the command line, including token budgets and RTK filters for processing context. Switch saved server connections, import or export configurations, and inspect or expire conversation sessions.

• Adjust context token budgets and filtering rules
• Switch between saved server connections
• Import or export connection settings as JSON

Set up OmniRoute and manage its command-line configuration. Inspect and validate tool settings, manage environment variables, check for updates, and control automatic startup using commands that support both interactive and unattended setup.

• Setting up a provider and default model
• Inspecting and validating CLI tool settings
• Checking or changing environment variables

Synchronize OmniRoute configuration, provider connections, and settings with cloud storage. Manage authentication for the cloud worker, a remote service, along with its credentials and remote backup destinations.

• Synchronize OmniRoute settings with cloud storage
• Initialize cloud synchronization
• Update cloud worker credentials

Inspect local AGNTCY integration settings and summarize endpoint configuration, the optional SLIM package, transport status, and session counters in a short table. Distinguish available components from unimplemented features without making network calls or changing settings.

• Check whether AGNTCY is configured
• Review SLIM package and endpoint settings
• Inspect mod counters for the current project

Audit important pages for settings that interfere with search indexing, including noindex directives, HTTP headers, and robots.txt rules. Identify accidental restrictions, suggest configuration fixes, and guide follow-up checks in Google Search Console.

• Investigating important pages missing from Google Search
• Checking for leftover staging restrictions after launch
• Reviewing CMS indexing settings for pages and categories

Check and fix hreflang tags, which identify language and regional versions of web pages for search engines. Review rendered HTML and HTTP responses to find missing reciprocal links, incorrect language codes, and fallback settings.

• Auditing language and regional page settings
• Checking reciprocal links between language versions
• Reviewing fallback page settings