wrkflw CLI
wrkflw validates and runs GitHub Actions locally, showing job dependencies and logs before changes reach hosted CI.
- 3,340 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- wrkflw runs workflow commands with configured secrets; emulation can execute them directly on the host.
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/wrkflwDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- wrkflw runs workflow commands with configured secrets; emulation can execute them directly on the host.
This is third-party code. Review the repository files before installing.
What it does
wrkflw validates GitHub Actions files and runs jobs in a selected local runtime. Users can check structure, execute a workflow or select one job, with a terminal dashboard for progress and logs. It handles dependencies, matrices and change-aware filtering. Container, host and Kubernetes execution are available. Local success helps debugging but does not establish full GitHub runner equivalence.
Who it is for. CI engineers testing GitHub Actions changes locally before pushing them.
Good fit when
- Changed YAML needs structural validation before commit.
- You want to reproduce one failed job without running the whole workflow.
- Repeated workflow edits need a local watch loop.
- A team wants task dependencies and execution logs in the terminal.
Not a fit when
- A test requires exact Windows or macOS runner behavior.
- The workflow relies on automatic service-container startup.
- You need enforced concurrency groups and cancel-in-progress behavior.
Example request
Validate our workflow and propose running one job in Docker. Identify unsupported fields before execution.Limitations
Auto mode tries Docker and Podman before falling back to host execution; select the intended runtime explicitly when execution boundaries matter. Service containers are parsed but never started in any runtime. Concurrency groups and cancellation of previous runs are parsed without enforcement. Remote reusable workflows from private repositories are unsupported because cloning uses unauthenticated HTTPS.
How to disable. Stop execution or watch mode and inspect created containers or pods. Remove unused local secret access.
FAQ
How do I validate without running jobs?
Run `wrkflw validate` and inspect findings before execution.
What does auto do without containers?
wrkflw runs the jobs directly on the host machine. If that is unsuitable, choose a specific container runtime beforehand.
Can I select one job?
Yes. Use `--job` or TUI selection and inspect its dependencies.
Is Kubernetes auto-selected?
No. It is explicit and fails without host fallback if the cluster is unavailable.
How do I list discovered workflows?
Run `wrkflw list` and verify the project directory and files.
Discussion
No questions or reviews yet.
Related
CLI toolsGitHub Actions workflows run on your machine, and a failing step pauses so the agent can fix the file and retry it.
A gh extension for agentic workflows: describe a task in Markdown and run it with an agent in GitHub Actions
Run Gemini CLI
run-gemini-cli
Google's official action for GitHub Actions: runs Gemini CLI in a repository to review pull requests, triage issues and edit code
A GitHub Action that runs Claude Code in pull requests and issues: answers mentions, reviews and makes changes
A local gate in front of git push: the branch goes through review, tests, docs and lint in a separate worktree before it reaches the remote with a PR
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
README in short
Gitea workflows and GitLab validation or remote triggering are also supported. Secret providers are configurable.