Skip to content
Skills Library
DevOps & cloud · Review & audit

github-actions-review

/github-actions-review

Review GitHub Actions workflows for correctness, security, and maintainability. Use when reviewing GitHub Actions workflow PRs, checking workflow security, evaluating CI/CD pipeline design, or assessing permissions and secret handling.

Licence
Apache-2.0
Last repository change
18.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
18
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Review GitHub Actions workflows for correctness, security, and maintainability. Use when reviewing GitHub Actions workflow PRs, checking workflow security, evaluating CI/CD pipeline design, or assessing permissions and secret handling.

Original author description

Review GitHub Actions workflows for correctness, security, and maintainability. Use when reviewing GitHub Actions workflow PRs, checking workflow security, evaluating CI/CD pipeline design, or assessing permissions and secret handling.

How it works

  1. Input
  2. Output Specification
  3. Execution Scope
  4. Reference Files Guide
  5. Workflow
Original SKILL.md headings · 59 lines, 303 words
SKILL.md preview
---
name: github-actions-review
description: >-
  Review GitHub Actions workflows for correctness, security, and maintainability.
  Use when reviewing GitHub Actions workflow PRs, checking workflow security,
  evaluating CI/CD pipeline design, or assessing permissions and secret handling.
license: Apache-2.0
metadata:
  author: y-miyazaki
  version: "1.1.1"
---

## Input

- Workflow YAML and/or composite action YAML (`action.yml`) + PR context (required)

## Output Specification

Return structured Markdown in accordance with [references/common-output-format.md](references/common-output-format.md). That file is the source of truth for the output contract.

## Execution Scope

- Systematically apply review checklist from [references/common-checklist.md](references/common-checklist.md)
- Do not modify workflow files or approve/merge PRs

### USE FOR:

- review workflow security and correctness with human judgment
- assess trigger design, permissions, and secrets handling
- review multi-workflow PRs for policy and maintainability risks

### DO NOT USE FOR:

- execute syntax/security validators (`actionlint`, `ghalint`, `zizmor`)
- auto-fix workflow YAML files
- replace deterministic workflow validation checks

## Reference Files Guide

- [common-checklist.md](references/common-checklist.md) (always read)
- [common-output-format.md](references/common-output-format.md) (always read)
- [category-global.md](references/category-global.md) (always read)
- [category-ordering.md](references/category-ordering.md) (always read)
- [category-security.md](references/category-security.md) (always read)
- [category-best-practices.md](references/category-best-practices.md) (always read)
- [category-error-handling.md](references/category-error-handling.md) (always read)
- [category-performance.md](references/category-performance.md) (always read)
- [category-tool-integration.md](references/category-tool-integration.md) (always read)
- [common-troubleshooting.md](references/common-troubleshooting.md) (read on failure)

## Workflow

1. Read PR context and workflow intent; extract events, `permissions`, secret usage, and external action references.
2. Apply the full review checklist and collect failed/deferred items.
3. Order issues in output by severity: `SEC-*` first, then correctness, then maintainability.
4. Output report with the required sections per [references/common-output-format.md](references/common-output-format.md). Include file path, line reference, and remediation step for each issue.

### Error Handling

| Condition                             | Severity    | Action                                                                                                |
| ------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------- |
| `common-checklist.md` unavailable     | Fatal       | Stop, report missing dependency                                                                       |
| `common-output-format.md` unavailable | Recoverable | Note missing file; emit `## Checks Summary`, `## Checks (Failed/Deferred Only)`, and `## Issues` only |
| PR contains no workflow YAML files    | Recoverable | Report "no reviewable workflows" and stop                                                             |

### Examples

- Prompt: `Review workflow PR and report failed/deferred checks`
- Result: Structured report per [references/common-output-format.md](references/common-output-format.md); each issue includes path, line, and remediation.
Files in this package (18)
  • SKILL.md 3 KB
  • eval.yaml 1 KB
  • evals/tasks/github-actions-review-basic.yaml 1 KB
  • evals/tasks/github-actions-review-boundary-guardrail.yaml 1 KB
  • evals/tasks/github-actions-review-specific-check.yaml 1 KB
  • evals/tasks/github-actions-review-structured-output.yaml 1 KB
  • evals/tasks/github-actions-review-trigger-negative.yaml 1 KB
  • references/category-anti-patterns.md 2 KB
  • references/category-best-practices.md 1 KB
  • references/category-error-handling.md 1 KB
  • references/category-global.md 1 KB
  • references/category-ordering.md 1 KB
  • references/category-performance.md 1 KB
  • references/category-security.md 2 KB
  • references/category-tool-integration.md 1 KB
  • references/common-checklist.md 2 KB
  • references/common-output-format.md 4 KB
  • references/common-troubleshooting.md 1 KB

Versions

The database has no other skills named github-actions-review.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 26dc60e418e3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100workflow-audit
    Audit GitHub Actions workflows for correctness, security, and unattended reliability. Use when asked to audit workflows, check CI health, review workflow security, or before committing workflow changes.
  • 100review-ci
    Use when the user asks for a CI review, CI/CD review, GitHub Actions review, workflow review, pipeline review, build pipeline audit, "review the workflows", "review the actions", action pinning audit, workflow permissions audit, or supply-chain review of CI configuration.
  • 100github-actions
    Use when adding CI/CD, creating workflows, auditing GitHub Actions, or fixing action pinning. Creates and audits workflows for SHA pinning and permissions.
  • 100github-actions
    GitHub Actions workflow review, scaffolding, and security hardening. Use when user says 'review my workflow', 'check my actions', 'scaffold a workflow', 'is my CI correct', 'pin actions', 'OIDC to AWS', or when working in .github/workflows/*.yml files.
  • 90code-review
    Review a code diff for correctness, regressions, security, compatibility, and maintainability. Use when asked to review a proposed or completed change.
  • 100github-actions-style
    GitHub Actions workflow and composite action conventions for MLflow. Use when writing, modifying, or reviewing workflows in .github/workflows/ or actions in .github/actions/ in this repository.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.