'actions' 검색 결과

Set up CodeQL security scanning in GitHub Actions or with the local CLI. Get guidance on language settings, build steps, analysis rules, result uploads, and troubleshooting so you can configure scans and interpret their findings.

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

• Adding security scans to GitHub Actions
• Running local scans with the CodeQL CLI
• Investigating failed builds or result uploads

Set up gh-aw, a GitHub CLI extension that turns Markdown workflows into GitHub Actions. The skill provides installation options and points agents to further instructions for creating, updating, debugging, and optimizing those workflows.

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

• Setting up gh-aw
• Turning Markdown workflows into GitHub Actions
• Finding guidance for workflow creation and updates

Investigate Next.js security issues across Server Actions, middleware, image optimization, and cached pages. Provides testing workflows for authentication bypass and data exposure, with checks to distinguish actual vulnerabilities from normal responses.

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

• Checking authentication in Server Actions and middleware
• Testing image optimization for unintended server requests
• Inspecting page data for sensitive information

Review build and deployment pipelines for unsafe workflows, exposed credentials, and configuration flaws across GitHub Actions, Jenkins, GitLab CI, and Terraform state files. Use concrete evidence and false-positive checks to distinguish exploitable issues from suspicious settings.

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

• Review GitHub Actions workflows for unsafe execution paths
• Investigate Jenkins exposure and affected versions
• Check logs, artifacts, and container images for leaked secrets

Windows 데스크톱 앱을 직접 조작하는 자동 테스트를 만듭니다. 화면 요소 식별, 표시 대기, 실패 기록과 CI 연동을 다룹니다.

• Windows 앱 조작 테스트 작성
• 결과가 불안정한 GUI 테스트 조사
• 화면 요소에 안정적인 식별자 추가

코드 변경 시 테스트, 타입 검사, 빌드를 자동 실행해 배포 전 품질 확인 절차를 마련합니다. GitHub Actions 설정부터 단계적 배포와 롤백 절차까지 다룹니다.

• 새 프로젝트에 CI 도입하기
• 테스트와 품질 검사 자동화하기
• 단계적 배포와 롤백 설계하기

Create and improve GitHub Actions workflows for automated testing and deployment. Coordinate multiple AI agents to review pull requests, investigate failed runs, scan for security issues, and manage releases across repositories.

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

• Create workflows for automated testing and deployment
• Investigate failed runs and suggest fixes
• Coordinate code reviews and security checks

Discover what a paired phone or wearable currently supports, then run the requested device, app, camera, media, or smart-home action. Check each device's published capabilities and permissions, and report the actual outcome or any execution errors.

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

• Check which actions a paired device supports
• Run supported device controls or app actions
• Use available camera or media actions

Inspect project files to identify languages and build tools, then generate starter GitHub Actions or GitLab CI workflows. Set up automated checks, caching, and deployment stages that reflect the project’s commands and target environments.

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

• Setting up automated checks for a new project
• Reworking fragile pipeline configuration
• Moving between GitHub Actions and GitLab CI

Investigate failed pull request checks in GitHub Actions using the GitHub CLI. The skill gathers logs, summarizes failures, proposes a repair plan, and applies changes after explicit approval, with a summary of changes and tests.

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

• Investigating failed GitHub Actions checks
• Reviewing a repair plan before approving changes
• Summarizing failure logs for a pull request

Set up automated testing before implementation begins. Detect the configured game engine, create test folders and runner configuration, and prepare a GitHub Actions workflow so tests can run automatically on each push.

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

• Set up automated testing before the first sprint
• Create test folders and runner configuration
• Prepare GitHub Actions to run tests on each push

Classify a failed NemoClaw GitHub Actions job using logs with sensitive information hidden and output size limited. Optionally inspect saved artifacts to identify failure patterns and gather evidence for further investigation.

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

• Classifying a failed GitHub Actions job
• Inspecting saved artifacts for failure evidence
• Gathering initial evidence for an E2E failure

Monitor GitHub Actions builds and tests with the gh command-line tool. Track runs until completion, inspect branch or pull request checks, read failed job logs, and rerun failed jobs or entire workflows.

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

• Watch a build or test run until completion
• Check workflow status for a branch or PR
• Read logs from failed jobs

Build Next.js 14+ applications with App Router, server-rendered components, and form actions. Produces routes, page layouts, data fetching, loading and error states, and SEO metadata, while supporting performance optimization and deployment preparation.

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

• Building pages and layouts with App Router
• Implementing form submissions with Server Actions
• Adding loading states, error handling, and SEO metadata

Configure Convex deployment environment variables for secrets such as API keys, read them from application actions, and check the configured values while keeping secrets out of source code and Git.

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

• Setting API keys for a Convex deployment
• Reading secrets from actions
• Managing separate values for each deployment

Audits GitHub Actions workflows that run AI coding agents. Traces how attacker-controlled content reaches prompts, checks permissions and sandbox settings, and reports evidence, severity, and fixes for prompt injection and related configuration risks.

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

• Reviewing workflows that run AI coding agents
• Tracing issue and PR content into agent prompts
• Checking sandbox settings and user allowlists

Inspects GitHub repositories, pull requests, issues, reviews, and automated Actions runs through the connected iPolloWork service. Combines remote information with the local checkout, summarizes relevant evidence, and routes review fixes, CI investigation, or publishing to specialist workflows.

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

• Understanding the status of pull requests and issues
• Routing unresolved review feedback to a specialist workflow
• Starting an investigation of failing GitHub Actions

Review CI/CD pipelines, the workflows that build and release software, for unsafe code execution, exposed secrets, and excessive permissions. Combine automated scanning with manual checks to document reproducible findings and suggested fixes.

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

• Reviewing GitHub Actions workflows
• Checking secrets and token permissions
• Inspecting self-hosted runners

Guide Peekaboo releases through GitHub Actions, from version and changelog preparation to a publication rehearsal and authorized release. Verify published downloads, npm packages, Homebrew details, and follow-up updates against the hosted build.

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

• Prepare version and changelog updates for a release
• Rehearse the release workflow without publishing
• Publish an explicitly authorized release

Analyze TRES Finance transactions to find repeated fees, rewards, and small entries worth combining. Propose and validate daily or monthly aggregation rules, create approved rules, and list existing rules or delete pending ones to simplify ERP records.

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

• Consolidating frequent gas fees
• Grouping staking rewards into monthly entries
• Reviewing aggregation proposals before ERP integration

Create a shareable TRES Finance Transactions link filtered by dates, wallets, assets, amounts, and other requested conditions. The skill checks filter values and URL formatting so customers or colleagues can reopen the specified view.

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

• Share a filtered transaction view with a customer
• Review transactions for selected wallets
• Find failed transactions within a date range

Use when configuring Slack-specific Agentforce capabilities AFTER the basic Slack deployment is complete: enabling Slack-native actions, managing public vs. private action scope, mapping Salesforce-to-Slack user identity, or troubleshooting Slack action failures. Triggers: 'add General Slack Actions topic to agent', 'configure canvas creation for Agentforce in Slack', 'Agentforce private action requires user identity mapping', 'Slack agent cannot send DMs after deployment', 'Agentforce Look Up User action not working in Slack', 'how to map Slack users to Salesforce identities for private actions'. NOT for the initial Slack OAuth install, DM vs channel-mention mode, or core agent setup — use agentforce/agent-channel-deployment. NOT for sending a Slack message or creating a channel from a Flow — use flow/flow-for-slack.

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

GitHub Actions のワークフロー実行エラーを調査し、原因を特定して解決策を提案する。「Actions エラー」「ワークフロー失敗」「CI が落ちた」「ビルド失敗」「テスト失敗」「Actions を調べて」「CI のエラーを見て」などで起動。失敗したジョブのログを分析し、具体的な修正方法を提示。

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

Create, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.

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