Wrkflw

---

title: wrkflw type: tool created: 2026-05-16 last_updated: 2026-05-16 related: ["Playradar"] sources: ["https://github.com/bahdotsh/wrkflw"] radar_quadrant: Tools radar_ring: Assess radar_position: center

wrkflw

A command-line tool for validating and executing GitHub Actions workflows locally, built in Rust. Enables developers to test CI/CD workflows on their own machines before pushing to GitHub.

Core Capabilities

Validation:

• Syntax and structural checks on workflow YAML files
• Composite action input cross-checking
• Diff-aware filtering — runs only jobs affected by changed files
• CI/CD-friendly exit codes for integration into pre-push hooks

Execution:

• Multiple runtimes: Docker, Podman, emulation mode, and a sandboxed secure mode
• Individual job selection with automatic dependency resolution
• Parallel execution of independent jobs
• Watch mode for automatic reruns on file changes

Expression Support:

• Evaluates ${{ ... }} syntax including toJSON, fromJSON, contains, startsWith
• GitHub context emulation (environment variables, output management)
• Full matrix build support with include, exclude, max-parallel, and fail-fast

Advanced:

• Docker container actions, JavaScript actions, and composite actions
• Reusable workflows (local and remote) with output propagation
• Artifact upload/download and inter-job output passing
• Secrets management: environment variables, file, Vault, AWS, Azure, GCP

Installation

cargo install wrkflw
brew install wrkflw

Key Commands

wrkflw validate path/to/workflow.yml
wrkflw run --runtime docker .github/workflows/ci.yml
wrkflw run --job build --workflow-file workflow.yml
wrkflw watch --event pull_request --base-branch main

Comparison to act

act (nektos/act) is the established tool in this space. wrkflw offers a similar feature set with a broader runtime abstraction (Podman, sandboxed mode) and a richer expression evaluator. Both require Docker for full workflow execution. wrkflw is newer and less battle-tested than act.

Radar Assessment

wrkflw sits in the Assess ring of the Tools quadrant, at center position. First studied via the GitHub repository on 2026-05-16; no personal use. Local GitHub Actions execution is a well-understood problem space with established alternatives (act). Center position reflects that a trial is feasible — the tool installs via Cargo or Homebrew and covers a broad feature set — but is held there by the availability of act as a more proven alternative and the requirement for Docker to execute most workflows. Worth trialling on a project with complex matrix builds or composite actions where act falls short.