Engineering is full of mechanical work that has to happen but doesn't require thinking. Bumping dependencies. Cleaning up Docker images. Writing the changelog. Running the test suite before pushing. None of these are hard. All of them steal time and attention from actual problem-solving.

ClawFlows ships twelve workflows specifically for developers, each one targeting a mechanical chore that engineers do dozens of times a week. This roundup covers all twelve, what they do, and which ones deliver the highest time savings per invocation.

Key Takeaways

ClawFlows includes 12 dev-focused workflows in the Dev Tools category of nikilster/clawflows.
Each workflow automates a repetitive engineering chore — dependency checks, Docker cleanup, changelog generation, test runs, and more.
They compose with the rest of the 113-workflow collection, so you can stack them with focus mode, standup, and security routines.
The highest-leverage ones are check-dependencies, docker-cleanup, and build-changelog based on time savings per invocation.
All workflows are open source and easily forkable for your specific stack.

The Twelve Workflows

Here's the full list, with a brief on what each one does.

1. check-dependencies

Audits your NPM, pip, or package dependencies for security vulnerabilities, outdated versions, and license issues. Generates a report you can act on. Covered in depth in Check-Dependencies: NPM Security Automation.

Run it: Weekly, or before any release.

2. docker-cleanup

Reclaims disk space by removing unused Docker images, stopped containers, and dangling volumes. On a busy dev machine, this saves 40GB a month easily. We profile it in Docker Cleanup Workflow Saves 40GB Monthly.

Run it: Weekly, or when your machine is running hot.

3. build-changelog

Generates a changelog from your Git commit history since the last tag. Groups commits by type (feat, fix, docs, refactor) and outputs markdown ready to paste into a release. See Build Changelog: Release in 60 Seconds.

Run it: Before every release.

4. run-tests-before-commit

Runs your test suite, linter, and type checker before you commit. Blocks the commit if anything fails. Essentially a structured pre-commit hook that's smarter than the standard Husky setup.

Run it: Every commit (can be wired as a hook).

5. create-pr

Builds a pull request with a generated title and description based on your branch's commits. Auto-links related issues, assigns reviewers from your CODEOWNERS, and pushes the branch if needed.

Run it: Whenever you're ready to merge a feature.

6. audit-env-files

Scans your .env and config files for secrets that shouldn't be committed, duplicated keys, or missing required variables. Compares against a template to catch drift.

Run it: Before every deploy, or weekly.

7. clean-branches

Deletes local Git branches that have been merged to main or whose remotes no longer exist. Keeps your git branch list sane without manual pruning.

Run it: Weekly.

8. update-deps

Updates dependencies to the latest compatible versions, runs the test suite, and commits the changes if tests pass. A safer version of npm update that verifies nothing breaks.

Run it: Monthly, or when you have time to review.

9. scaffold-project

Creates a new project from a template — directory structure, package.json, README, CI config, license. Faster than any create-[framework]-app CLI because it's customized to your house style.

Run it: Whenever starting a new project.

10. run-benchmarks

Runs your benchmark suite and compares against the last stored result. Highlights regressions and improvements in a readable diff.

Run it: Before optimization work, and after.

11. rebase-main

Handles the mechanics of rebasing your feature branch onto latest main — fetch, rebase, force-push if needed. Aborts cleanly if there are conflicts.

Run it: Before opening a PR.

12. reset-dev-env

Wipes and rebuilds your local dev environment — node_modules, build caches, Docker layers, virtualenv. Useful when something's mysteriously broken and you don't want to debug it.

Run it: When the dev env is haunted.

The Three Highest-Leverage Ones

If you only install three of the twelve, make them:

check-dependencies — the security value alone justifies it
docker-cleanup — the disk savings add up fast
build-changelog — saves 15 minutes per release, every release

These three hit the intersection of high frequency and high effort-saved per invocation. The others are valuable but more situational.

How They Compose With Other Workflows

Dev workflows are most useful when they're part of a release routine. A common pattern:

run-tests-before-commit — verify clean state
check-dependencies — no new vulns
build-changelog — draft the release notes
create-pr — open the PR
After merge: clean-branches — tidy up

That's five workflows that collapse about 20 minutes of manual work into roughly 90 seconds of invocations. We cover orchestration patterns in How Workflows Orchestrate Multiple Skills.

Customizing for Your Stack

The default workflows assume a Node.js project with Git and Docker. If you work in Python, Rust, Go, or something more exotic, you'll want to fork and customize. Most of the workflows are 20-50 lines of structured definition, so adapting them is fast.

The nikilster/clawflows repo has examples of community forks for Python and Rust stacks in the discussions.

FAQ

Do these workflows work with monorepos?

Most do, with configuration. check-dependencies, build-changelog, and run-tests-before-commit all have flags for targeting a specific package within a monorepo. docker-cleanup is repo-agnostic.

Can I run them in CI?

Yes. ClawFlows workflows can be invoked from GitHub Actions, GitLab CI, or any CI system that runs OpenClaw. Many teams use them to keep local and CI behavior consistent.

What about Windows developers?

All twelve work on Windows, though a few (docker-cleanup, clean-branches) assume a POSIX-like shell. WSL handles this cleanly.

Is there a workflow for database migrations?

Not in the core 12, but community forks exist for Prisma, Drizzle, and Alembic migration workflows. Check the workflows channel for community contributions.

Where do I find the source for these?

All twelve live in the dev-tools category of nikilster/clawflows on GitHub. Each workflow is a single file with a description, metadata, and the step definitions.

Install the Dev Stack Today

If you're an engineer, these twelve workflows will save you more time in the first month than any productivity app you've tried. Install the full ClawFlows collection (see How to Install ClawFlows in One Command) and start with the three high-leverage ones. Within a week you'll wonder how you worked without them.

Explore all 113 workflows at aiskill.market/workflows or submit your own.

Sources

nikilster/clawflows on GitHub — source for all twelve dev workflows
OpenClaw platform
113 Workflows That Run Your Digital Life
Docker documentation
Anthropic Claude docs