'changes' 검색 결과

Run quality gates, commit, push, and open a PR with the canonical template. Use when the user runs /ship or wants to ship the current changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You are a dependency management expert specializing in safe, incremental upgrades of project dependencies. Plan and execute dependency updates with minimal risk, proper testing, and clear migration paths for breaking changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detects API surface changes in CI. PublicApiAnalyzers, Verify snapshots, ApiCompat gating.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement and refactor frontend features using Vue and Quasar with repository architecture, theming, UX, and performance standards. Use when tasks involve components, composables, Pinia, routing, i18n/UI behavior, responsive layouts, or frontend clean architecture changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and enforce privacy and data protection controls across application, API, and database layers. Use when tasks involve PII handling, retention/deletion policies, consent, data minimization, auditability, or compliance-oriented architecture changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design, implement, and stabilize automated tests (unit, integration, E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design, implement, and stabilize automated tests in this repository (unit, integration, and E2E) for .NET/C#, Rust, APIs, and frontend flows. Use when the user asks to create tests, increase coverage, fix flaky tests, or validate behavior changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Base implementation skill. Use for code changes, bug fixes, refactors, and script work across .NET/C#, backend APIs, database/ORM, Vue/Quasar frontend, Rust, PowerShell, Docker, K8s, CI/CD, security, observability, and SRE domains. Specialized skills extend this as a base.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Implement MYOT changes safely with minimal diffs, behavior preservation, and post-change validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Documentation and narrative content. USE FOR: writing docs; markdown files; storybook stories; vitepress guides; API documentation. DO NOT USE FOR: production code changes (use code-implementation skill); tests (use test-writing skill); commit conventions (use commit-conventions skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Unit and integration testing strategy. USE FOR: writing tests; coverage improvements; vitest specs; test refactoring. DO NOT USE FOR: production code changes (use code-implementation skill); documentation (use documentation skill); commits (use commit-conventions skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when reading or changing example.com content, settings, products or pricing through the MCP API at /api/mcp — the 27 JSON-RPC tools, how to authenticate, which changes need a redeploy and which are live immediately, and the commercial scope rule that the product tools enforce.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detect DCSync attacks where adversaries abuse Active Directory replication privileges to extract password hashes by monitoring for non-domain-controller accounts requesting directory replication via DsGetNCChanges.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detect unauthorized modifications to running containers by monitoring for binary execution drift, file system changes, and configuration deviations from the original container image.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configures host-based intrusion detection systems (HIDS) to monitor endpoint file integrity, system calls, and configuration changes for security violations. Use when deploying OSSEC, Wazuh, or AIDE for endpoint monitoring, building file integrity monitoring (FIM) policies, or meeting compliance requirements for change detection. Activates for requests involving HIDS configuration, file integrity monitoring, OSSEC/Wazuh deployment, or host-based detection.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs. Identifies wallet clusters, tracks fund movement through mixers and exchanges, and supports law enforcement attribution. Activates for requests involving ransomware payment tracing, bitcoin wallet analysis, cryptocurrency forensics, or blockchain intelligence gathering.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Executes malware samples in Cuckoo Sandbox to observe runtime behavior including process creation, file system modifications, registry changes, network communications, and API calls. Generates comprehensive behavioral reports for malware classification and IOC extraction. Activates for requests involving dynamic malware analysis, sandbox detonation, behavioral analysis, or automated malware execution.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scan the project for refactoring opportunities, then fix them. No behavior/visual changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create or update product-update / release-notes content for a given OpenMetadata/Collate patch version across getcollate, openmetadata-site, and docs-om. Sources getcollate's changelog from openmetadata-collate + OpenMetadata + ai-platform; openmetadata-site's from OpenMetadata only; docs-om reuses openmetadata-site's already-written content, reformatted into its Mintlify snippet structure. Filters to customer-facing changes only, runs each target's own doc-review checklist, verifies every link live, and requires explicit approval before any commit.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Configure and deploy Workflow Launchers that automatically start workflows in response to JCR content changes on AEM as a Cloud Service

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply a Content Driven Development process to AEM Edge Delivery Services development. Use for ALL code changes - new blocks, block modifications, CSS styling, bug fixes, core functionality (scripts.js, styles, etc.), or any JavaScript/CSS work that needs validation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create effective content models for your blocks that are easy for authors to work with. Use this skill anytime you are building new blocks, making changes to existing blocks that modify the initial structure authors work with.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Compare two versions of an AEM Edge Delivery Services page to identify what changed. Fetches preview vs live, or two different URLs, and produces a detailed content diff showing added, removed, and modified content, metadata, and blocks. Use when reviewing changes before publishing, auditing content modifications, or tracking content evolution.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.