render-migrate-from-heroku
Migrate from Heroku to Render by reading local project files and generating equivalent Render services. Triggers: any mention of migrating from Heroku, moving off Heroku, Heroku to Render migration, or switching from Heroku. Reads Procfile, dependency files, and app config from the local repo. Optionally uses Heroku MCP to enrich with live config vars, add-on details, and dyno sizes. Uses Render MCP or Blueprint YAML to create services.
Install
With your agent
Install OMGSkills skill "render-oss/render-plugin-claude-code:skills/render-migrate-from-heroku" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/render-oss/render-plugin-claude-code /tmp/render-plugin-claude-code && ln -s /tmp/render-plugin-claude-code/skills/render-migrate-from-heroku ~/.claude/skills/render-migrate-from-heroku
From README
Heroku to Render Migration Migrate from Heroku to Render using the user's supplied inventory or local project files, then optionally enrich missing details with live Heroku data via MCP. Prerequisites Check Before starting, verify what's available: App inventory (required) — use complete details supplied by the user, or inspect local project files such as Procfile, app.json, package.json, requirements.txt, Gemfile, or go.mod Render MCP (recommended) — check if listservices tool is available. Required for MCP Direct Creation (Step 3B) and automated verification (Step 6). Not required for the Blueprint path — the Render CLI and Dashboard handle generation, validation, and deployment. Heroku MCP (optional) — check if listapps tool is available Do not require local files or MCP when the user has already supplied enough information for the requested plan, Blueprint, or migration instructions.
More from this repo
render-background-workers
Sets up and configures background workers on Render for queue-based job processing.
render-blueprints
Authors and validates render.yaml Blueprints for Render infrastructure.
render-cli
Installs and uses the Render CLI for deploys, logs, SSH, psql, Blueprint validation, and automation.
