Validates GitHub Actions workflow changes in this monorepo using actionlint, conftest policy checks, spotless formatting, and act testability assessment. Use when creating, editing, or reviewing workflow files.
89
—
Does it follow best practices?
Impact
85%
2.57xAverage score across 3 eval scenarios
Passed
No known issues
Use this skill for every workflow modification.
actionlint .github/workflows/*.ymlconftest test --rego-version v0 -o github --policy .github .github/workflows/*.yml./mvnw spotless:apply -T1C.claude/skills/act-testing/references/workflow-tiers.md and the rubric in .claude/skills/act-testing/SKILL.md..claude/skills/act-testing/SKILL.md before proceeding.test-*.yml harness, run check-drift.sh, assess act feasibility (act, docker, daemon), and provide user-run scenario commands.test-*.yml files only after user-run act validation is complete.act directly against production workflows.Do not skip step 1.
For every changed workflow, include:
workflow: <path>tier: <1|2|3>reason: <single sentence>evidence: <drift-check + feasibility + scenario matrix | tier-3 rationale>For Tier 1/2 workflows, evidence must explicitly contain:
test-workflow: <path>drift-check: <command + result>feasibility: act/docker/daemonscenario-matrix: <positive + negative at minimum>act-commands: <copy-paste ready plain text using canonical format: act <event> -e <event-json> -W <test-workflow> --secret-file .secrets --reuse; full workspace-relative paths; no markdown links in command text>cleanup: <test harness removed or justification>If these fields are missing, validation is incomplete and should not be reported as done.
actionlint + conftest + spotlessactionlint + conftest + spotless + actactionlint + conftest + spotless + rationaleCI: actionlint (workflows)CI: conftest (workflows policy)CI: verify skill markdown stability5dd956f
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.