From solo-dev-suite
Scans a codebase for local-to-cloud migration blockers -- hardcoded paths, LAN URLs, dev-only bypasses, missing deploy configs -- and produces a scored readiness report. Triggers on "deploy readiness", "ready to deploy", "can I host this", "cloud migration check", "scan for local stuff", "deployment blockers". Part of the solo-dev-suite -- loads the project profile via the orchestrator. Unlike security-audit (a checklist), this skill actually reads code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/solo-dev-suite:deploy-readinessThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scans a codebase for things that will break when you move from local development to cloud hosting. Not a checklist -- an automated scanner that reads your code and reports concrete findings with file paths and line numbers.
Scans a codebase for things that will break when you move from local development to cloud hosting. Not a checklist -- an automated scanner that reads your code and reports concrete findings with file paths and line numbers.
solo-dev-suite/profiles/<slug>.jsonrepository_path set (or use --path override)8 categories, each targeting a specific class of local-to-cloud blocker:
.fmr.local, .local hostnames, localhost, 127.0.0.1, private/LAN IPs (192.168.x.x, 10.x.x.x)D:\laragon\..., C:\xampp\..., /home/user/... absolute pathsAPP_ENV === 'development' gates, hardcoded test credentials (admin/admin).env.example* or localhost-only CORS policiesmove_uploaded_file, writeFileSync to local upload dirsnode_modules/, vendor/, .git/, dist/, build/, __pycache__/package-lock.json, *.lock)python scripts/deploy_readiness_tool.py scan <slug>
python scripts/deploy_readiness_tool.py scan <slug> --path /alternate/repo
python scripts/deploy_readiness_tool.py scan <slug> --json
Walks the repo, scans every source file, checks repo structure, writes the sidecar. Re-running overwrites the previous scan.
python scripts/deploy_readiness_tool.py show <slug>
python scripts/deploy_readiness_tool.py show <slug> --category hardcoded-urls
python scripts/deploy_readiness_tool.py show <slug> --json
Human-readable output with status icons, severity tags, file:line locations, and matched code.
python scripts/deploy_readiness_tool.py resolve <slug> --item URL01
python scripts/deploy_readiness_tool.py resolve <slug> --item URL01 --status wont-fix --notes "Dev-only config file"
Status values: resolved, wont-fix. Recalculates the score after each resolution.
python scripts/deploy_readiness_tool.py render <slug> [--output-dir <path>]
Generates DEPLOY_READINESS.md with summary table, per-category findings, and severity indicators.
python scripts/deploy_readiness_tool.py delete <slug> --yes
Removes the sidecar.
After every scan, profile.deploy_readiness_model is updated:
{
"last_scan_at": "...",
"score": 72,
"score_label": "ALMOST",
"total_findings": 15,
"criticals": 2,
"highs": 4
}
Also updates last_skill_run["deploy-readiness"].
deploy-readiness/
├── SKILL.md # this file
├── .claude-plugin/
│ └── plugin.json # plugin metadata
└── scripts/
└── deploy_readiness_tool.py # scan / show / resolve / render / delete
python scripts/deploy_readiness_tool.py scan my-project
python scripts/deploy_readiness_tool.py scan my-project --path D:/laragon/www/crumble
python scripts/deploy_readiness_tool.py show my-project
python scripts/deploy_readiness_tool.py show my-project --category hardcoded-urls
python scripts/deploy_readiness_tool.py resolve my-project --item URL01
python scripts/deploy_readiness_tool.py render my-project
python scripts/deploy_readiness_tool.py delete my-project --yes
Expected: scan finds .fmr.local, localhost, D:\laragon paths in typical local-dev projects. Score reflects severity. Resolve marks items and recalculates.
npx claudepluginhub frobinson47/solo-dev-suite --plugin feature-enhanceProvides CDSS development patterns for drug interaction checking, dose validation, clinical scoring (NEWS2, qSOFA), and alert classification integrated into EMR workflows.