'cicd' 검색 결과

Create and improve GitHub Actions workflows that automate building, testing, and deployment. The skill covers testing across multiple environments, dependency caching, build output management, and security settings such as limited permissions and protected deployment environments.

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

• Create a build, test, and deployment workflow
• Run automated tests on pull requests
• Configure tests across multiple environments

Set up automated Android builds and Google Play publishing with GitHub Actions. Supports TWA, React Native, Flutter, and native Android, with signing setup, separate testing and production tracks, and automatic build-number increments on main.

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

• Setting up Google Play publishing from GitHub
• Separating internal, alpha, beta, and production releases
• Automating versionCode increments on main

GitHub Actionsの自動チェック、Cloudflareのチーム用Account設定、非エンジニア向け資格情報登録、自動公開を安全に導入する。Codexで「CI/CDを設定」「Cloudflareを設定」「自動デプロイ」「$setup-cicd」と依頼されたときに使用する。

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

Generate and optimize CI/CD pipelines for GitLab CI and CircleCI. Use when a user asks to set up GitLab CI, create a CircleCI pipeline, build a CI pipeline for GitLab, automate deployments with CircleCI, add test automation to GitLab, or configure continuous integration on non-GitHub platforms. For GitHub Actions pipelines, use the github-actions skill instead.

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

Expert in integrating Claude Code with CI/CD pipelines. Covers headless mode for non-interactive execution, GitHub Actions and GitLab CI/CD integration, automated code review, issue triage, and PR workflows. Essential for teams wanting AI-powered automation in their development pipelines. Use when "claude code CI/CD, headless mode, GitHub Actions claude, GitLab CI claude, automated code review, PR automation, issue triage, claude-code, cicd, automation, github-actions, gitlab, headless, pipeline, devops" mentioned.

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

World-class continuous integration and deployment - GitHub Actions, GitLab CI, deployment strategies, and the battle scars from pipelines that broke productionUse when "ci/cd, cicd, pipeline, github actions, gitlab ci, circleci, jenkins, workflow, deployment, deploy, release, blue green, canary, rollback, build, test automation, continuous integration, continuous deployment, cicd, github-actions, gitlab-ci, deployment, automation, devops, pipelines, continuous-integration, continuous-deployment" mentioned.

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

Integrate AFL++ coverage-guided fuzz testing into CI/CD pipelines to discover memory corruption, input handling, and logic vulnerabilities in C/C++ and compiled applications.

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

Turn an existing GitHub Actions workflow into a structured specification for maintenance and AI reference. Document its purpose, triggers, job dependencies, inputs, outputs, permissions, and failure handling, focusing on expected behavior rather than implementation details.

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

• Documenting an existing GitHub Actions workflow
• Reviewing job order and dependencies
• Organizing permissions and failure handling

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

Investigate how credentials can be exposed in CI/CD, the systems that build and deploy software. Covers environment variables, logs, credential stores, cloud trust settings, and runner tokens, with methods to assess access scope and defensive controls.

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

• Review secret exposure in build environments
• Search build logs and caches for leaked credentials
• Assess trust settings between pipelines and cloud services

Assess security weaknesses in CI/CD systems that automate software builds and delivery. Covering GitHub Actions, Jenkins, GitLab CI, and Azure DevOps, the skill examines unsafe inputs, excessive permissions, exposed credentials, and tampered build outputs, alongside detection and defensive controls.

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

• Reviewing workflow inputs and execution triggers
• Assessing pipeline permissions and credential exposure
• Checking build artifact handoffs for tampering risks

Create and edit EAS workflow YAML files to automate builds and deployments for Expo projects. Check required settings, job dependencies, and dynamic values against the latest schema, which defines the accepted configuration.

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

• Create an automated build workflow for an Expo project
• Edit EAS deployment automation
• Check workflow settings and job dependencies

CI/CD pipeline security hunting — GitHub Actions workflow injection, secret exfiltration, self-hosted runner poisoning, dependency confusion, OIDC token theft, and supply chain attacks. Covers sisakulint scanning, manual workflow analysis, and chaining CI/CD bugs into critical findings. Use when a target has public repos, GitHub Actions, CircleCI, Jenkins, or GitLab CI.

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

Hunt cloud / infrastructure misconfigurations. AWS: public S3 buckets (s3:GetObject anonymous), permissive bucket policies (PutObjectAcl public-write), exposed CloudFront origin, public Lambda function URL, public RDS snapshot, IAM credentials in JS bundles, AWS metadata accessible via SSRF. GCP: public GCS buckets, exposed Cloud Run services, leaked service account JSON. Azure: public blob containers, exposed Function App. (Kubernetes/Docker exposure is owned by hunt-k8s; CI/CD pipeline attacks by hunt-cicd; post-credential IAM escalation by cloud-iam-deep.) Detection: targeted dorking, certificate transparency, JS bundle secret extraction, port scan for known service ports. Validate: actual data read / write / RCE. Use when hunting cloud-native storage and compute misconfig (S3/GCS/Blob, IMDS-via-SSRF, serverless, public managed services).

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

Hunt CI/CD pipeline vulnerabilities — GitHub Actions workflow injection (pull_request_target Pwnrequest + ${{ }}-into-shell), self-hosted runner poisoning, OIDC trust-policy abuse, Jenkins script-console RCE and CVE-2024-23897 file read, GitLab CI runner-token registration, Terraform state file leakage, artifact/log secret leakage, pipeline env-var disclosure. Use when target has a public GitHub/GitLab org, exposed CI dashboards (Jenkins/TeamCity/Drone/Argo), or build artifacts/images are reachable.

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

Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.

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

You are a workflow automation expert specializing in creating efficient CI/CD pipelines, GitHub Actions workflows, and automated development processes. Design automation that reduces manual work, improves consistency, and accelerates delivery while maintaining quality and security.

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

OWASP CI/CD Top 10 knowledge base for identifying, assessing, and remediating CI/CD pipeline security risks.

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

Write a CI/CD pipeline playbook for a service or team. Use when asked to document a CI/CD pipeline, write a deployment process, define release gates, document build and test stages, or create a deployment guide. Produces a structured playbook covering pipeline stages, environment definitions, deployment gates, rollback procedures, and on-call responsibilities.

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

Runs the Fabric Git integration lifecycle through fab api or az rest, including connecting a workspace to Azure DevOps or GitHub, committing, updating from Git, reading sync status, resolving conflicts, disconnecting a connected workspace, and automating sync with a service principal. For stage promotion use deployment-pipelines-authoring-cli. Branch switching, fab deploy, fabric-cicd and cross-workspace rebinding are out of scope.

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

Creates an ALM (Application Lifecycle Management) plan for deploying a Power Pages site across environments. Gathers your promotion strategy, target environments, and approval requirements upfront, then generates a visual HTML plan document for your review and approval. **plan-alm does not deploy anything itself** — it is a planner. After you approve the plan, run the individual ALM skills (setup-solution, setup-pipeline, deploy-pipeline, or export-solution/import-solution); each detects the approved plan and executes the right step in order, keeping the plan updated as it runs. Use when asked to: "plan my alm", "set up alm", "create deployment plan", "plan my deployments", "help me deploy to multiple environments", "set up promotion strategy", "create cicd plan", "plan site promotion", "help me go to production", "set up pipeline for my site".

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

CI/CD pipeline design methodology, deployment strategies, GitHub Actions patterns, and branch/release strategies. Load when designing pipelines or deployment workflows.

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

Rollback procedures, risk assessment, pre/post-deployment validation, and contingency planning. Load when orchestrating deployment or preparing rollback plans. For deployment strategy details (canary, blue-green, rolling), see `cicd-and-deployment` skill.

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

Set up CI/CD pipelines for Flutter apps. Use when configuring automated testing, build, or deployment workflows with GitHub Actions or Fastlane.

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