「change」の検索結果

Run ADR conformance checks, explain failures, and identify required ADR/doc updates for the current change.

日本語の概要は準備中です。原文の説明を表示しています。

Documentation structure and maintenance rules for the Megahub project. Use whenever making user-facing changes — adding features, changing behavior, fixing hardware compatibility, or modifying configuration. Describes which files to update, the README structure, and writing style.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews Laravel migrations for destructive operations, change() dropping modifiers, locking index creation on large tables (PostgreSQL), and asymmetric down().

日本語の概要は準備中です。原文の説明を表示しています。

Ensure design/ADR changes include a concrete migration plan, rollout strategy, rollback conditions, and compatibility considerations.

日本語の概要は準備中です。原文の説明を表示しています。

Ensure architecture updates document affected stakeholders, notification plan, and deprecation/retirement signals to keep knowledge aligned.

日本語の概要は準備中です。原文の説明を表示しています。

Ensure design changes stay consistent across ADRs, diagrams, and specs; decisions are traceable; and drift is explicitly managed.

日本語の概要は準備中です。原文の説明を表示しています。

Ensure architecture/design docs define clear boundaries, ownership, dependency direction, and change impact to avoid tight coupling.

日本語の概要は準備中です。原文の説明を表示しています。

Ensure API/contract changes specify versioning strategy, backward compatibility, deprecation plan, and migration guidance.

日本語の概要は準備中です。原文の説明を表示しています。

Ensure code changes keep logs/metrics/traces useful for debugging failures and regressions.

日本語の概要は準備中です。原文の説明を表示しています。

Enforce null/undefined safety for changed TypeScript code and suggest safer patterns.

日本語の概要は準備中です。原文の説明を表示しています。

Find missing tests for critical paths, edge cases, and failure handling in changed code.

日本語の概要は準備中です。原文の説明を表示しています。

Review changes to the Agent Skills import/export bridge for path safety, round-trip fidelity, and validation correctness.

日本語の概要は準備中です。原文の説明を表示しています。

Apply OpenClaw visual identity to logos, typography, imagery, voice, documents, presentations, social graphics, and launch materials. Use when the task changes brand identity rather than ordinary product UI or public-page composition.

日本語の概要は準備中です。原文の説明を表示しています。

Review a repository change for correctness, security, and maintainability.

日本語の概要は準備中です。原文の説明を表示しています。

Prepare a precise handoff for unfinished repository work.

日本語の概要は準備中です。原文の説明を表示しています。

Configure the studio, brand, and generation tools. Use on a missing-config report, or when the user says "set up manticore", "change my tools", or "update my studio".

日本語の概要は準備中です。原文の説明を表示しています。

Override default column types in materializations using castToString or custom DDL. Use when column type needs different precision (e.g., NUMERIC(22,6)), VARCHAR length is wrong, need JSONB instead of JSON, integers lose precision, or need to force a string representation. Use when user says "change column type", "wrong precision", "VARCHAR too short", "integer truncated", "cast to string", or "custom DDL".

日本語の概要は準備中です。原文の説明を表示しています。

Add or define specific fields in a collection's readSchema. Use when fields are missing from materialization field selection, pruned by complexity limit, need type refinement, need to be protected from future inference changes, or need to be required for downstream consumers. Use when user says "missing fields", "pruned fields", "field not showing up", "complexity limit", "define field in read schema", "restrict field type", or "protect field from inference".

日本語の概要は準備中です。原文の説明を表示しています。

FlutterSecureStorage (v10.x) for encrypted key-value storage of sensitive data using platform-native secure enclaves with biometric authentication support. Use this skill when storing OAuth tokens (access tokens, refresh tokens, ID tokens), API keys and secrets, user passwords or PINs, session tokens, encryption keys, private keys for cryptography, certificate data, biometric enrollment data, banking credentials, health data, or any sensitive information requiring platform-level encryption (iOS Keychain with Secure Enclave, Android Keystore with Hardware-backed keys). Supports Touch ID, Face ID, and Android biometric prompt integration. Handles biometric change invalidation (resetOnError), data migration from SharedPreferences/EncryptedSharedPreferences, Google Drive backup exclusion, automatic key rotation, configurable encryption algorithms (AES), and prevents data extraction even on rooted/jailbroken devices. Essential for authentication flows, secure credential management, or compliance requirements (PCI DSS, HIPAA, GDPR data protection).

日本語の概要は準備中です。原文の説明を表示しています。

Control risky structural change by proving a refactor is necessary and that behaviour, contracts, data, security boundaries, and operational properties can be preserved through a staged migration. Use whenever the user wants to refactor, restructure, clean up, modernise, extract, migrate, rewrite, or re-architect existing code, or asks whether they should. Prefer this over starting the refactor. DO NOT REFACTOR is a first-class outcome. Part of the audit suite; inherits the shared constitution while its own job is proving necessity and behavioural preservation.

日本語の概要は準備中です。原文の説明を表示しています。

Manage semantic version updates for rad-mem project. Handles patch, minor, and major version increments following semantic versioning. Updates package.json, marketplace.json, plugin.json, and CLAUDE.md version number (NOT version history). Creates git tags and GitHub releases. Auto-generates CHANGELOG.md from releases.

日本語の概要は準備中です。原文の説明を表示しています。

Distills enduring architectural decisions and design rationale from wave orchestration plans or historical git changes into structured, tracked Architecture Decision Records (ADRs). Use pre-wave to resolve active architectural constraints or post-wave to record enduring decisions in docs/decisions/.

日本語の概要は準備中です。原文の説明を表示しています。

Fetch the latest upstream branch and merge it into the current branch, in the claude-statusline repo — feature branches (`dev-<feature>`) sync from `dev`, and `dev` itself syncs from `master`. Stages the merge, walks through any conflicts interactively, then creates the signed merge commit directly. Use whenever the user says "sync", "pull dev", "pull master", "update branch", "merge dev", "merge master", "get latest", or anything about bringing upstream changes into their working branch — even if they don't say the word "skill".

日本語の概要は準備中です。原文の説明を表示しています。

Review, harden, and test the safety policy for AI-Controlled Party mixer/Soundcraft Ui24R scene arming. Use for approval gates, blocked mixer operations, hazardous request handling, venue validation, bypass attempts, QA, risk review, or follow-up safety changes.

日本語の概要は準備中です。原文の説明を表示しています。