인프라·DevOps 스킬

Diagnose installation and configuration problems in oh-my-claudecode, including version mismatches, duplicate legacy hooks, and missing runtime requirements. Receive a status report with recommended fixes, with confirmed repairs preserving unrelated settings and custom content.

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

• Diagnosing problems after installation
• Checking configuration after an update
• Investigating duplicate legacy hooks

Define repeatable workflows and their dependencies in JSON, then execute them through a CLI. Combine commands, read-only agent tasks, parallel branches, and human approval steps, with journal records that support recovery after interruption.

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

• Running repeatable build and test workflows
• Resuming a workflow after a crash
• Adding human approval before deployment

Retrieve an EagleEye traceId, an identifier linking a request across logs, using Arthas without changing application code. Observe request-handling methods, capture parameters when needed, and inspect method calls and timings to investigate problems.

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

• Retrieving a request's traceId without code changes
• Matching request parameters with related logs
• Inspecting method calls and execution times

Monitor selected GitHub Actions checks on an SGLang pull request until they pass on its latest commit. Diagnose failures, push small validated fixes, and retry only failed jobs within defined limits.

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

• Monitor selected PR checks until they pass
• Separate code failures from infrastructure problems
• Apply small fixes and track the resulting checks

Launch an SGLang server, run a quick accuracy check, and capture an execution trace for performance inspection. Return the trace location and generated files, ready to open in Perfetto or Chrome tracing.

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

• Capture an execution trace of SGLang inference
• Check basic accuracy before profiling
• Record input processing and token generation separately

Prepare batches of merged SGLang pull requests for a release branch. It checks conflicts and previous attempts, starts the cherry-pick workflow, monitors completion, and reports created pull requests or failure reasons.

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

• Prepare multiple merged PRs for a release branch
• Check conflicts before starting workflows
• Detect previous cherry-pick PRs

Calculate how to divide serving memory between recurrent state and KV cache, two memory pools used by hybrid models. Use startup logs and workload settings to recommend a ratio, estimate concurrency, and identify the limiting pool.

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

• Choosing a memory ratio for a hybrid model
• Investigating limits on concurrent requests
• Recalculating memory allocation for context length

Collect and review SGLang startup logs to identify unnecessary output and trace its source. Get saved logs and specific cleanup proposals while preserving useful diagnostics, with runtime changes left for user approval.

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

• Investigating repeated messages in startup logs
• Checking which startup warnings need attention
• Comparing startup logs across models and GPU counts

Understand and modify SGLang's CI pipelines, including test stage order, start conditions, early stopping after failures, and workload splitting. Use the guide to add jobs and investigate failed, skipped, or cancelled checks.

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

• Add a test job to an SGLang CI stage
• Investigate failed or skipped CI checks
• Update test partitions and waiting job counts

Investigate SGLang serving failures by collecting server state, preserving failing requests, and replaying them on a clean target. Summarize evidence and likely causes, then choose the next debugging tool for crashes, stalls, or performance regressions.

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

• Investigate failed health checks and growing queues
• Reproduce request-specific timeouts or crashes
• Investigate output changes after deployment

Prepare a local Terraform environment by checking installation, choosing a macOS or Linux installation method, initializing configuration folders, and validating files. It also addresses plugin download failures and common initialization errors.

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

• Install Terraform for the first time
• Fix a missing terraform command
• Initialize and validate a folder containing .tf files

Find installation steps, configuration guidance, and command examples for Alibaba Cloud CLI using local Chinese documentation. The skill checks its quick reference or relevant documentation pages before suggesting commands, parameters, and options.

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

• Look up installation and configuration steps
• Check commands for querying ECS instances
• Find output filtering and pagination options

Design and review infrastructure managed with Terraform or OpenTofu. Get guidance on reusable modules, testing choices, automated deployment workflows, and security checks, with approaches suited to different software versions and the cost of running tests.

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

• Designing reusable infrastructure modules
• Choosing infrastructure testing methods
• Setting up automated infrastructure deployment

Set up encrypted connections between devices with Tailscale and control access by user or device. The skill covers network routing, device name resolution, and self-hosting the coordination server with Headscale.

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

• Replacing a traditional VPN with Tailscale
• Restricting server access by team or device
• Connecting remotely to internal networks

Configure Google Cloud IAP to check identity before granting access to internal applications and virtual machines. Set permissions by user group, device, and network, configure reauthentication, enable service-account access, and record access decisions for monitoring.

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

• Replacing VPN access to internal Google Cloud applications
• Restricting sensitive tools to managed devices
• Configuring SSH and RDP access through IAP tunnels

Configure AWS Verified Access for VPN-free access to internal applications. Combine user identity and device security checks, write Cedar access policies, and use Terraform and AWS RAM to deploy and share access controls across AWS accounts.

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

• Replacing VPN access to internal applications
• Writing policies based on users and device security
• Deploying Verified Access with Terraform

Configure pfSense to separate internal, guest, DMZ, and IoT networks. Set firewall rules, port forwarding, VPN connections, and bandwidth policies, then check traffic logs and test that each network can reach only its intended destinations.

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

• Separate staff, guest, server, and IoT networks
• Set port forwarding rules for externally accessible services
• Configure VPN access and bandwidth policies

Configure TLS 1.3, a protocol for encrypted connections, on nginx, Apache, and Python applications. Select encryption settings and key exchange groups, disable outdated protocols, and use openssl s_client and testssl.sh to check connections and configuration weaknesses.

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

• Enabling TLS 1.3 on nginx or Apache
• Configuring encrypted connections in a Python application
• Disabling outdated TLS versions and weak encryption

Set up Cloudflare Access and Tunnel to protect internal applications using user identity and device health checks. Covers application access policies, WARP device enrollment, and audit logging for teams replacing VPN access.

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

• Replace VPN access with application-specific permissions
• Expose internal apps without opening inbound ports
• Limit contractors to approved applications

Deploy Prisma Access to secure access to internal applications for remote users and branches. Configure connectors, GlobalProtect agents, access policies based on user groups and device security, and centralized logging through Strata Cloud Manager.

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

• Migrating VPN and branch security to Prisma Access
• Restricting internal app access by user and device
• Integrating access controls with existing Palo Alto NGFW systems

Deploy a Software-Defined Perimeter that connects verified users to authorized applications. Configure single-packet authorization, mutual certificate authentication, access policies, and monitoring, then test whether unauthorized connections and access between applications are blocked.

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

• Building zero trust access to internal applications
• Hiding services from unauthenticated network scans
• Testing certificate authentication and access restrictions

Build a GitLab CI/CD pipeline with automated checks for vulnerable code, dependencies, container images, running applications, and exposed secrets. Covers scanner configuration, consolidated findings, and approval policies for serious vulnerabilities before production deployment.

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

• Add automated security scans to .gitlab-ci.yml
• Check dependencies and container images for known vulnerabilities
• Detect credentials and API keys committed to source control

Configure SAML identity federation, a way to share authentication between systems, linking on-premises Active Directory with Microsoft Entra ID. Cover single sign-on for cloud applications, user attribute mapping, authentication model choices, and signing certificate management.

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

• Extending on-premises authentication to cloud resources
• Comparing authentication models for hybrid identity
• Setting up SAML single sign-on for SaaS applications

Prepare an AionUi release by checking AionCore assets, updating versions, and generating a changelog. Run quality checks, create a pull request with automatic merging enabled, then tag the merged release to trigger its build.

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

• Releasing the next AionUi patch version
• Releasing with explicitly chosen UI and Core versions
• Preparing a frontend-only release