「dependency」の検索結果

Code review for the current change, before it is pushed. One command runs the security, secret, dependency and lint scanners that fit the changed files, a separate reviewer that checks every scanner finding and is given every changed line, and prints a short receipt with the path of the full report. Use before every git push, when asked for a code review, a security scan, or to review changes, a diff or a pull request, and when a push was blocked or warned by OpenQodex.

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

Use when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.

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

Use when scaffolding a project, refactoring into layers, creating view models/repositories, configuring dependency injection, or implementing unidirectional data flow (MVVM).

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

Enhanced Mikado Method for complex architectural refactoring - systematic dependency discovery, tree-based planning, and bottom-up execution

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

Use for software supply-chain security assessment covering SBOM, SCA, CI/CD pipelines, container images, build integrity, dependency provenance, and vulnerability reachability.

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

Use when the user wants to roll back GSD commits: the last N, a whole phase, or one plan. Reverts through the phase manifest with dependency checks and a confirmation gate before anything is undone.

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

Use before /gsd-manager to fill in missing Depends on fields in ROADMAP.md. Analyzes file overlap, semantic dependencies and data flow between phases, then suggests dependency updates to confirm.

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

Use when the user wants to execute a phase's plans, resume the remaining plans, or run only one wave. Discovers plans, groups them into dependency waves, spawns a fresh subagent per plan, then verifies the phase.

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

Generate a Disaster Recovery plan with RTO/RPO targets. Use when someone asks to "create a DR plan", "disaster recovery", "business continuity", or "RTO RPO". Do NOT use for step-by-step restoration runbooks — use /pmstudio-recovery instead. Designed for SaaS platform products where Coco Inc is the customer — focuses on service continuity, data recovery, and vendor dependency management rather than infrastructure rebuild.

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

Break a plan, spec, or conversation into dependency-aware, independently verifiable tickets. Use explicitly when the user wants work sliced for local planning or an issue tracker.

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

Builds dependency-ordered delivery plans from requirements and repository evidence; read-only.

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

Upgrades dependencies in reversible batches with version-specific compatibility and regression checks.

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

Audits PR diffs for architecture boundary violations, design simplicity, dependency drift, and established-pattern mismatches. Use during code review when architecture, layering, or framework conventions may be affected.

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

Write React hooks with clean effect boundaries and measured memoization. Use when working with `useEffect`, custom hooks, refs, transitions, or hook dependency problems in React.

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

Apply core coding standards, dependency injection, and configuration for Spring Boot 3. Use for Spring Boot application structure and DI/configuration; defer Spring Security hardening and test-specific setup to their focused skills.

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

Configure PHP ecosystem tooling, dependency management, and static analysis. Use when managing Composer dependencies, running PHPStan, or configuring PHP build tools.

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

Test Python services with pytest, async coverage, monkeypatch, and boundary-focused fakes. Use when writing Python tests, fixtures, async tests, regression tests, or dependency-isolated verification.

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

Secure Python services against secret leakage, injection, unsafe subprocess calls, and dependency drift. Use when handling env vars, tokens, SQL, file paths, shell commands, auth flows, or Python security gates.

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

Configure Python tooling, dependency surfaces, static analysis, and verification gates. Use when editing `pyproject.toml`, `requirements.txt`, `pytest.ini`, `ruff`, `pyright`, CI, or Python release checks.

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

Idiomatic JavaScript patterns and conventions for maintainable existing code. Use when reviewing or refactoring JavaScript language patterns; defer project scaffolding, dependency setup, and tool configuration.

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

Implement reactive state with GetX controllers, bindings, and observables in Flutter. Use when managing app state with GetxController, Obx, GetBuilder, or dependency lifecycle—not unit tests for existing controllers.

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

Enforce inward dependency flow, pure domain layers, and DTO-to-entity mapping in Flutter DDD architecture. Use when structuring layers or boundaries; defer navigation-only routing and feature implementation such as notifications.

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

Compose modern Flutter layouts and widgets idiomatically. Use for widget trees, layout constraints, mounted safety, and UI composition—not BLoC state management, routing, dependency injection, or tests.

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

Structure Go code with package-first boundaries, `cmd/` and `internal/`, and explicit dependency wiring. Use when shaping project layout, package ownership, or service boundaries in Go; defer Redis/cache-specific implementation recipes to database skills.

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