DevFlow — Developer Workflow Automation CLI
One tool to scaffold, audit, fix, and ship any project.
Stop Wasting Hours on Project Setup
Every developer knows the pain:
- Starting a new project means hours of boilerplate — config files, CI/CD, linting, testing, Docker
- Code reviews catch formatting and lint issues that should have been fixed automatically
- Shipping a release means bumping versions, updating changelogs, tagging, building — all manual and error-prone
DevFlow replaces 10+ separate tools with 4 commands.
What DevFlow Does
devflow init — Smart Project Scaffolding
Creates production-ready projects with best practices baked in:
- Python (CLI, API, library), Node.js, and full-stack templates
- Pre-configured linting (ruff), formatting (black), type checking (mypy), and testing (pytest)
- GitHub Actions CI/CD ready to go
- Docker config included
- Automatic git init and initial commit
- Sensible defaults you can override
$ devflow init my-api --template api --description "REST API for widget tracking"
$ devflow init my-cli --template cli
$ devflow init my-saas --template fullstack --description "My SaaS app"
devflow audit — Codebase Health Check
Comprehensive project audit that checks:
- Project structure and conventions
- Linting violations (ruff)
- Code formatting (black)
- Import organization (isort/ruff)
- Test coverage and passing status
- Docstring coverage
- Security vulnerabilities (bandit)
- Hardcoded secrets
- Dependency freshness and known vulnerabilities
$ devflow audit
# 72/100 — 8 passed, 3 warnings, 1 error
$ devflow audit --format markdown --severity error
$ devflow audit --format json # for CI integration
devflow fix — Auto-Fix Everything
One command to fix all the issues audit found:
- Format code with black
- Sort imports with ruff/isort
- Fix lint violations
- Preview with
--dry-runbefore applying
$ devflow fix --dry-run # See what would change
$ devflow fix --apply # Fix everything
$ devflow fix --scope format # Just fix formatting
devflow ship — Release Automation
Ship a release in one command:
- Runs audit first (quality gate — blocks release on errors)
- Bumps version (patch/minor/major)
- Updates CHANGELOG.md
- Creates git tag
- Builds distribution packages
- Optionally pushes to remote
$ devflow ship --bump patch --message "Fix login bug"
$ devflow ship --bump minor --message "Add user dashboard" --push
$ devflow ship --bump major --dry-run # Preview before shipping
Why Developers Buy DevFlow
- Save 2-4 hours per project setup. Stop copy-pasting configs between projects.
- Catch issues before code review. Audit and fix in your editor, not in PR comments.
- Ship with confidence. Automated quality gates prevent broken releases.
- One tool, not ten. Replace black, isort, ruff, flake8, bandit, pip-audit, bumpversion, and manual changelogs.
- CI-ready output. JSON and markdown formats integrate with any pipeline.
Installation
pip install kryptorious-devflow
Requires Python 3.9+.
Quick Start
# Create a new project
devflow init my-project --template cli
# Check its health
cd my-project
devflow audit
# Fix any issues
devflow fix --apply
# Ship v0.1.0
devflow ship --bump patch --message "Initial release"
What You Get
- Full source code — MIT-licensed, modifiable, extensible
- 6 project templates — Python CLI, API, Library, Node.js, Full-stack, and Generic
- Pre-configured tooling — ruff, black, mypy, pytest, GitHub Actions CI
- Docker support — Dockerfile and docker-compose included for all templates
- Lifetime updates — All 1.x updates included
Requirements
- Python 3.9 or later
- Git (for init and ship commands)
- Optional: black, ruff, bandit, pip-audit (devflow tells you what to install)
License
Proprietary — single-user license. See LICENSE for terms.
Support
Email: support@devflow.sh Docs: https://devflow.sh/docs
Built with DevFlow itself. Ship everything.
Metadata
Release files for kryptorious-devflow 1.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| kryptorious_devflow-1.5.1.tar.gz | 31.5 kB | Without provenance | Details for kryptorious_devflow-1.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kryptorious_devflow-1.5.1-py3-none-any.whl | Python 3 | none | any | Details for kryptorious_devflow-1.5.1-py3-none-any.whl |
Total release size: 64.3 kB
Release files / kryptorious_devflow-1.5.1.tar.gz
| Download URL | kryptorious_devflow-1.5.1.tar.gz |
|---|---|
| Size | 31.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
45b39202f803bd169ab9aac730037f6cf1ad9a28da3f80c1f16da04f3217fcce
|
|
BLAKE2b-256 checksum How to use checksums |
b6a211a85327f089f506ee3a564a7814c5674149e1b6c50a23be1aef16f26862
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / kryptorious_devflow-1.5.1-py3-none-any.whl
| Download URL | kryptorious_devflow-1.5.1-py3-none-any.whl |
|---|---|
| Size | 32.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f18be3f04c05a8abeb25a90d50d8938973603fb9020470e1d04f992fdab635e
|
|
BLAKE2b-256 checksum How to use checksums |
62129cf5b9604f560efa131678d64cf989730ce8f217ab4a205c0ff7780b878e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for kryptorious-devflow 1.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.