Update GitHub Actions versions in workflow files, focusing only on major version changes. Use when the user wants to update action versions, check for outdated GitHub Actions, or upgrade workflow dependencies to their latest major versions.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Update action versions in GitHub Actions workflow files, focusing on major version changes only.
v4) automatically fetches the latest minor and patch versions.actions/checkout@v4 will automatically get versions like v4.2.2, v4.3.0.v4 to a specific version like v4.2.2 — this is unnecessary.v5 to v6).Note: Skip
fatjyc/update-submodule-action@v6.0updates as the new version is broken.
Look for files in .github/workflows/ recursively. Note that composite actions may be used — read both the composite action and the calling workflow simultaneously.
Analyze the action versions used in the workflow files.
Query each action's latest version:
https://github.com/{owner}/{repo}/releases/latest
Only update actions where the major version has changed:
docker/build-push-action@v5 → @v6actions/checkout@v4 → @v4.2.2Note: Skip
fatjyc/update-submodule-action@v6.0updates as the new version is broken and v6.0 is fine.
For actions requiring updates, retrieve changelogs to understand breaking changes.
Update version numbers and make adjustments for any breaking changes.
Git add and commit your changes with a clear message indicating the updates made.
# From
uses: docker/build-push-action@v5
# Update to
uses: docker/build-push-action@v6
# From
uses: actions/checkout@v4
# Incorrectly updated to
uses: actions/checkout@v4 .2 .2
# Keep unchanged
uses :actions / checkout @ v 4
GitHub will automatically use the latest v 4.x.x release
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Add SLSA build-provenance attestations to existing GitHub Actions workflows. Use when the user wants to add artifact attestations, build provenance, or SLSA attestations to Docker container image builds in GitHub Actions CI/CD pipelines.
日本語の概要は準備中です。原文の説明を表示しています。
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
日本語の概要は準備中です。原文の説明を表示しています。
Guideline for designing, implementing, and verifying secure APIs following OWASP API Security Top 10 (2023) best practices. Use when the user wants to: (1) review API code or design for security vulnerabilities, (2) design a secure REST, GraphQL, or gRPC API architecture, (3) implement API authentication and authorization (OAuth2, JWT, API keys, mTLS), (4) configure rate limiting, input validation, or CORS, (5) audit API endpoints for BOLA, BFLA, or mass assignment vulnerabilities, (6) create API security checklists or verification plans, (7) fix API security bugs or harden existing APIs, (8) set up API security testing (OWASP ZAP, Schemathesis, Burp Suite), or (9) handle any API security concern including SSRF prevention, resource consumption limits, business flow protection, API inventory management, and secure third-party API consumption.
日本語の概要は準備中です。原文の説明を表示しています。
Write, review, and optionally test Bash and Zsh shell scripts following project coding standards. Use for ANY shell scripting task: (1) creating a new Bash or Zsh script, (2) editing, fixing, or reviewing an existing .sh, .bash, or .zsh file, (3) adding error handling, dependency checks, or cleanup traps to shell scripts, (4) implementing API integration or file processing in shell, (5) writing or fixing ShellSpec tests (spec/*_spec.sh), or (6) deciding whether a script should be written in Bash or Zsh. Defaults to Bash; Zsh-specific guidance lives in a reference file that is loaded only when writing Zsh.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Create, run, and maintain API test collections using Bruno (OpenCollection YAML format and legacy Bru format). Use when the user wants to: (1) create a Bruno API test collection from scratch or from OpenAPI/Swagger specs, (2) write API request files with tests and assertions, (3) run API tests using bru CLI, (4) generate test reports (HTML, JUnit, JSON), (5) set up CI/CD pipelines (GitHub Actions) for automated API testing, (6) debug or fix failing Bruno API tests, (7) add environment configurations for API testing, (8) chain API requests with data extraction, or (9) work with any .yml/.bru Bruno collection files. Triggers on mentions of 'Bruno', 'bru CLI', 'API testing collection', 'OpenCollection', or requests to automate API testing with file-based collections.
日本語の概要は準備中です。原文の説明を表示しています。