'patching' 검색 결과

Configure tools and skills for sub-agents before dispatching development tasks. Role presets cover implementation, planning, reviews, testing, and verification, with defined boundaries for what each agent should do and whether it may modify files.

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

• Setting tool permissions before spawning a sub-agent
• Separating implementation, planning, and review roles
• Configuring agents for review without file changes

Guide malware cleanup on infected Windows and Linux systems after containment and investigation. Covers removing malicious files and mechanisms that preserve attacker access, rotating credentials, patching entry points, and documenting validation results before recovery.

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

• Cleaning infected systems after containment
• Removing mechanisms that preserve attacker access
• Rotating compromised credentials and fixing entry points

Split independent debugging or repair tasks among multiple AI agents. Define a focused scope, constraints, and expected report for each agent, then review their changes, check for conflicts, and test the combined result.

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

• Investigating unrelated failures across test files
• Assigning separate subsystems to different agents
• Writing focused tasks with clear constraints

Diagnose OpenCLI commands broken by website changes, collect execution traces, patch the adapter that connects to the site, and retry. After a verified repair, prepares a GitHub issue for submission with user approval.

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

• Repair commands broken by website layout changes
• Adapt to changed API responses
• Distinguish empty results from adapter failures

Plans, executes, and validates Google Kubernetes Engine upgrades for Standard and Autopilot clusters. Creates environment-specific upgrade plans, checklists, and command-based runbooks, with guidance on maintenance timing, node upgrade strategies, workload readiness, and stalled upgrades.

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

• Planning a GKE version upgrade
• Choosing release channels and maintenance schedules
• Preparing node pool upgrades for databases or GPU workloads

Inspect GKE TPU Dynamic Slices, diagnose provisioning failures, and validate workload configuration for single slices or JobSet workloads spanning multiple slices. Get cleanup commands, with confirmation required before destructive changes.

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

• Checking TPU slice lifecycle states
• Diagnosing TPU slice provisioning failures
• Validating single-slice and multi-slice JobSet manifests

Read, create, and edit text files on the computer running the connected A0 CLI. The skill guides focused replacements and context-based patches, checking current file contents and handling read-only access or outdated edits.

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

• Read a text file on the connected local computer
• Replace a specific passage in an existing file
• Apply edits after file line numbers have shifted

Guides experiments that inspect and modify internal values in PyTorch models to study their effects on predictions. Covers local analysis and remote experiments through NDIF for models too large for local GPUs.

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

• Inspect internal values and attention patterns across layers
• Replace internal values to compare changes in predictions
• Run large-model experiments without local GPUs

Deploy ClawHub to production or publish a stable CLI release to npm. Check prerequisites for the exact commit, run the release workflow, and verify the deployed behavior or published version with traceable release evidence.

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

• Deploy ClawHub to production
• Publish a stable ClawHub CLI version
• Check release prerequisites for a specific commit

Investigate independent bugs or test failures concurrently by assigning each problem area to a separate agent. Define clear boundaries and expected reports, then review the fixes, check for conflicts, and run the full test suite before integration.

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

• Investigate unrelated test failures in parallel
• Split independent subsystem bugs among agents
• Write focused assignments with clear boundaries

Helps decide whether to handle a task directly, create a subagent, or route it to an agent already familiar with the work. The choice depends on required background knowledge and whether plausible but incorrect results can be checked.

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

• Choosing who should handle a task
• Delegating self-contained research with verifiable sources
• Routing context-heavy reviews to an informed agent

Review how evidence can be altered during authorized security exercises on Windows and Linux. Covers logs, timestamps, memory, disk records, and network traces, alongside the signs defenders use to detect manipulation.

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

• Planning authorized evidence manipulation tests
• Reviewing Windows and Linux forensic artifacts
• Checking detection coverage for altered evidence

Guides security testing of Android and iOS apps through file inspection and observation while the app runs. Covers network traffic, stored secrets, external app interfaces, authentication, and backend APIs, with tool examples and a testing checklist.

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

• Inspecting APK or IPA files for endpoints and embedded secrets
• Observing app behavior and traffic with Frida
• Reviewing deep links and externally accessible components

Collect posts from X search, profile, individual post, and list URLs. Organize text, authors, engagement counts, media, hashtags, and mentions into a consistent dataset, with support for collecting additional pages.

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

• Collecting posts from a mixed list of X URLs
• Monitoring posts from selected profiles and lists
• Gathering replies to a specific post

Manage Node.js dependencies with pnpm, from installing packages to coordinating multiple projects in one workspace. The skill covers shared version settings, third-party package patches, dependency overrides, and consistent installation procedures for automated build environments.

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

• Unifying dependency versions across a workspace
• Patching third-party packages and overriding versions
• Configuring package installation in CI

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

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

• Designing a new workflow through questions
• Investigating failed runs and recurring errors
• Upgrading workflows and addressing deprecations

Generate Beamer presentations for the sewage-house-prices project by dispatching the Storyteller agent (creator) and Discussant agent (critic). Supports 4 formats — job market, seminar, short, lightning. Derives all content from the paper.

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

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

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

DOCA-shipped Zero-Touch RoCE RTT congestion control (ZTR RTTCC) reference algorithm on a BlueField-3 DPA: deploy, tune and evaluate doca_pcc_dev_ztr_rttcc_algo through the shipped DOCA PCC sample. Trigger on "my RoCE-v2 flows aren't being throttled", "PCC sample isn't dispatching to my algo", "set-params returns fail", "algorithm loaded but counters are flat", "how do I pick the multipath PCC variant", or "do I need a custom CC algorithm on BF3", even without naming ZTR RTTCC. Your own algorithm through the host library belongs to doca-pcc; the doca_spcx_cc command line to doca-spcx-cc. Covers picking a variant (vanilla / PM / RX-rate / multipath / window-probeless) at DPACC build time, tuning host-set parameters, and DOCA_PCC_DEV_STATUS_FAIL from the algorithm. Refuse and route elsewhere for writing a custom PCC algorithm from scratch, read-only PCC counter inspection, or firmware-only pre-Programmable PCC.

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

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

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

Creates and automates custom image builds with EC2 Image Builder - Linux, Windows, and macOS AMIs, and container images to ECR. Covers the build IAM role, Amazon-managed and custom components, image recipes, infrastructure and distribution configuration (launch templates, SSM parameters, other Regions), one-off builds, recurring scheduled pipelines for golden AMI automation and OS patching, custom image workflows, and diagnosing failed builds. Applies when creating, automating, or scheduling AMI or container image builds with Image Builder, or when debugging a failed build. Not for launching instances from existing AMIs, AMI lifecycle/retirement, or general EC2 fleet management.

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

Evaluates, configures, and migrates workloads to AWS Lambda Managed Instances (LMI). Runs Lambda Event Functions (standard Lambda) on EC2 instances in the user's account while AWS manages provisioning, patching, scaling, routing, and load balancing. Triggers when queries mention Lambda Managed Instances, LMI, capacity providers, multi-concurrent execution environments, EC2-backed Lambda, persistent Lambda instances, PerExecutionEnvironmentMaxConcurrency, CapacityProviderConfig, cold start elimination via dedicated instances, migrating Lambda Event Functions to managed instances, or cost comparison between Lambda Event Functions and LMI with Savings Plans or Reserved Instances. Also covers long-running and asynchronous workloads and the 90-minute (5400s) function timeout for asynchronous and event-source-mapping (SQS, Kinesis, DynamoDB Streams / ESM) invocations, including how to raise the function timeout up to 90 minutes / 5400s and the related duration limits.

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

Operates Amazon MSK Provisioned clusters (Standard and Express brokers). Required for ANY MSK Provisioned task — training data conflates Standard and Express. Covers performance, consumer lag, storage, traffic shaping; sizing Standard vs Express; Kafka client tuning; CloudWatch alarms; cluster configs; maintenance, patching, rolling restarts; topic management; MSK Replicator setup for DR and active-active/active-passive replication (same-/cross-account), including throughput and partition sizing; Streaming Tables for S3 Tables and Data Delivery for General Purpose S3 — setup, IAM, monitoring. Prefer Flink for Kafka Iceberg sink questions. Migrations: use migrate-to-msk. Triggers: MSK Provisioned, Kafka, `kafka.*`/`express.*` types, AWS/Kafka namespace, cross-cluster replication, Kafka to Iceberg on S3 Tables, Kafka to S3, lakehouse, data lake from Kafka, Kafka Connect S3 Sink or Firehose alternative. DO NOT USE for MSK Connect — search docs instead. Serverless: only S3 Tables/data delivery eligibility.

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

Bug-fix discipline — every defect has an etiology, the chain of cause that produced the observable fault; trace it before patching. Errors only grow: a bandaid leaks unless genuinely localized and leak-free. Walk the diagnostic ladder (presentation → proximate cause → API contract → isolated or systemic) before writing the fix. Use when authoring or reviewing any bug fix, regression patch, "quick fix" PR, or when deciding whether to ship, defer, or refactor.

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