3.2K skills · sorted by relevance
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.
Update pnpm locally and align package.json with GitHub Actions settings. Check the published package and CI installation paths first, then record package integrity and pin the setup action to a specific commit.
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.
The English summary is being prepared. Showing the original description.
GitHub Actions のワークフロー実行エラーを調査し、原因を特定して解決策を提案する。「Actions エラー」「ワークフロー失敗」「CI が落ちた」「ビルド失敗」「テスト失敗」「Actions を調べて」「CI のエラーを見て」などで起動。失敗したジョブのログを分析し、具体的な修正方法を提示。
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Build and review Laravel web applications and APIs with clear separation of responsibilities. Covers Eloquent database models, input validation, consistent API responses, background jobs, events, and caching, helping organize application logic and data access.
Prepare Cline CLI releases for npm, the package registry, by reviewing SDK changes, drafting release notes, updating versions and changelogs, and creating release tags. Guides checks and publication through GitHub Actions or an authenticated local machine.
Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.
Investigate intermittent Remotion CI failures, record their error patterns in a tracking issue, and increment counts for repeated failures. Find failed checks even without a supplied pull request, then rerun affected GitHub Actions jobs.
Implement PR review actions already selected for fixes, run relevant checks, and create focused commits. Post progress and completion replies, resolve applicable threads, and update the action records and their Markdown summary.
Set up GitHub Copilot for a new project with instructions, reusable skills, and specialized agents tailored to its technology stack. Add a coding agent environment workflow when GitHub Actions is used, plus setup and customization guidance.
Review local uncommitted changes, verify findings, and repeat focused repairs until the review converges or a blocker remains. Also supports Qwen Code issue fixes and review responses within workflows run through GitHub Actions.
Build conversations and workflows with the Gemini Interactions API on Gemini Enterprise Agent Platform. Follow Python or JavaScript examples for server-stored conversation history, streaming responses, structured JSON output, function calls, and background agent tasks.
Design automated build, test, and deployment workflows for GitHub Actions, GitLab CI/CD, and Jenkins. Covers job ordering, dependency caching, secret handling, and gradual releases that use health checks before expanding deployment.
Investigate failed GitHub Actions jobs using logs and recent runs. Receive a report explaining the actual failure trigger, recurrence, any verified breaking commit, and existing pull requests that may fix the issue.
Check CI, the automated checks run on code changes, for the current branch alongside recent commits. Supports GitLab CI and GitHub Actions, with optional pull request or merge request numbers and links when command-line tools are unavailable.
Set up NuGet publishing from GitHub Actions using OIDC, an identity verification mechanism that provides short-lived tokens. Create or update the publishing workflow and get guidance for configuring the matching policy on nuget.org.
Guides the refactoring of large JavaScript files into smaller CommonJS modules within gh-aw. It covers source placement, function exports, tests, and action builds so extracted code remains testable and is included in generated actions.
Review and implement gh-aw workflows and Go code with security checks for untrusted input, shell commands, dependency versions, and permissions. The skill also covers event-specific conditions and tools that inspect workflows for errors and security risks without running them.
Helps configure Playwright tests in automated CI/CD pipelines across major providers. Covers splitting tests across runners, Docker execution, shared login setup, code coverage, and saving reports and debugging artifacts to investigate failures.
GitHub Actions の CI 失敗を検出・修正・再検証するスキル。 gh コマンドで PR の CI 状態を確認し、失敗時はログを取得して原因を分析、 コードを修正して push、CI が通るまでループする。 Use when: CI が落ちた、CI を直したい、PR のチェックが失敗している、 GitHub Actions のエラーを修正したい、CI を通したい。 Triggers: "CI", "ci-fix", "CI落ちた", "CI失敗", "checks failed", "GitHub Actions", "workflow failed", "CI通して", "CI修正"
The English summary is being prepared. Showing the original description.
GitHub Actions の CI 失敗を調査するスキル。失敗した run / PR / job の URL（例: https://github.com/OWNER/REPO/actions/runs/RUNID、…/pull/PR、…/job/JOBID）や run_id・PR 番号を貼られて「このCIが失敗している、原因を調査して」「ビルド/テストがコケた、なぜ落ちたか調べて」「workflow が failed、修正案を出して」「job のログを見て」と頼まれたら必ず使う。WebFetch では github.com のログは取れない（PreToolUse hook が差し戻し、HTML しか返らない）ため、gh（`gh run view --log-failed` / `gh run view --job` / `gh pr checks` / `gh api`）で失敗ジョブ・ステップと失敗ステップのログだけを決定論スクリプトで収集し、失敗原因を特定して修正案を提示する。GitHub Actions 以外（GitLab CI 等）や、URL がログではなくソース閲覧目的のときは対象外。GitHub(gh) 前提。`/gh-ci-investigate` で明示起動も可。
The English summary is being prepared. Showing the original description.
Test Discord bot access, message operations, and OpenClaw responses using leased QA bots. Collect API and Gateway evidence for replies, files, threads, reactions, streaming, and typing, while identifying interactions that require manual testing.