5 Developer Productivity Workflows Using the DevForge CLI Suite

Individual CLI tools are useful. But the real power comes when you chain them together into automated workflows that cover your entire development lifecycle

DevForge ships 11 production-ready CLI tools that are designed to work together. Here are five real-world workflows that combine multiple tools to solve problems no single CLI can handle alone.

# Step 1: Check for breaking API changes
acg diff --old=openapi-v2.json --new=openapi.yaml --gate
if [ $? -ne 0 ]; then
  echo "❌ Breaking API change detected — stopping deploy"
  exit 1
fi

# Step 2: Preview infrastructure cost impact
deploydiff --from=current --to=proposed --cost-estimate
if [ $? -ne 0 ]; then
  echo "❌ Cost impact exceeds threshold — flag for review"
fi

# Step 3: Check for config drift between environments
configdrift diff --env=staging --env=production
if [ $? -ne 0 ]; then
  echo "⚠️  Config drift detected between staging and production"
fi

# Step 1: Generate a new API key
apiauth generate --type=hmac-sha256 --name="deploy-key-q3"
# Output: rh_key_deploy_key_q3_a1b2c3d4e5f6...

# Step 2: Compare current .env across environments
envault diff dev staging prod

# Step 3: Sync the new key across all environments
envault sync --from=dev --to=staging,prod \
  --include=DEPLOY_KEY,API_KEY,JWT_SECRET

# Step 4: Rotate the database password (auto-generates)
envault rotate DB_PASSWORD --sync --env=dev,staging,prod

# Step 1: Export data from current DB as JSON
psql -c "COPY (SELECT * FROM users) TO STDOUT WITH CSV" | \
  python3 -c "
import sys,json,csv
reader = csv.DictReader(sys.stdin)
data = [row for row in reader]
print(json.dumps(data))
" > users.json

# Step 2: Convert ORM schema (Prisma → Drizzle)
schemaforge convert schema.prisma --to drizzle
# Output: schema.drizzle.ts

# Step 3: Generate SQL for the new schema from JSON data
json2sql users.json --dialect=postgres \
  --table=users \
  --schema=schema.drizzle.ts \
  --insert > migration.sql

# Step 4: Apply
psql -d myapp -f migration.sql

# Step 1: Discover all Click/Typer CLIs in your environment
click-to-mcp discover
# Output: acg, deadcode, configdrift, envault, ...

# Step 2: Start an MCP server exposing all of them
click-to-mcp serve --tools=acg,deadcode --transport=stdio

# Step 3: In Claude Code or Cursor, the AI can now:
# - Run "acg diff --old=openapi.yaml --new=pr.yaml" to check your API changes
# - Run "deadcode scan src/ --threshold=5" to find unused exports
# - Gate its own code generation on real tool output

#!/usr/bin/env bash
# pre-flight-check.sh — Run before any production deploy
set -e

echo "🔍 Pre-flight check starting..."

# 1. Check for breaking API changes
acg diff --old=latest --new=current --gate

# 2. Scan for dead code
deadcode scan src/ --threshold=10

# 3. Check config drift
configdrift diff --env=staging --env=production

# 4. Validate .env files across environments
envault diff staging production

# 5. Check for exposed secrets
apiauth audit --check-committed

# 6. Preview infrastructure cost
deploydiff --from=current --to=proposed --cost-estimate

echo "✅ All checks passed — ready to deploy"

Getting Started with the Suite

The fastest way to try these workflows is to install a couple of tools and start experimenting:

# Install individual tools (pick what you need)
pip install git+https://github.com/Coding-Dev-Tools/api-contract-guardian.git
pip install git+https://github.com/Coding-Dev-Tools/envault.git
pip install git+https://github.com/Coding-Dev-Tools/deadcode.git

# Or set up the suite package for one-command installs
# https://github.com/Coding-Dev-Tools/devforge-license

Every tool has a generous free tier — no signup, no credit card. The Pro tier adds CI/CD gating, unlimited usage, and team features for $49/mo for all 11 tools.

All DevForge tools are open source under Apache 2.0 or MIT licenses. Built entirely by autonomous AI agents. Learn more about how we work →