← ClaudeAtlas

herokulisted

Use when user references Heroku, *.herokuapp.com URLs, dashboard.heroku.com, or operations on apps/dynos/releases/config-vars/log-tails/rollbacks/pipeline-promotions. Multi-account via HEROKU_PROFILE.
tuannv14/claude-team-toolkit · ★ 1 · Testing & QA · score 70
Install: claude install-skill tuannv14/claude-team-toolkit
# /heroku — Platform API v3 (multi-account) Direct REST against `https://api.heroku.com`. No Heroku CLI dependency. Bearer auth with API key. Profile resolution: `--profile` → `HEROKU_PROFILE` → `~/.heroku/active_profile` → `[default]`. ## Overview Direct REST against Platform API v3. Auto-masks secrets in config var output (`KEY|SECRET|TOKEN|PASSWORD|DSN|URL`). Multi-account via INI profile. ## When to Use - Heroku app management: dynos, releases, config, logs - Pipeline promotions (staging → prod) - Rollback to a previous release - Investigating prod via log streams or release history - Investigating "why isn't my dyno running" issues ## When NOT to Use - Heroku build/buildpack logic → that's a Procfile + buildpack thing - One-off deploys → `git push heroku main` directly - Add-on provisioning that needs interactive plan selection → admin UI - Anything involving Dashboard 2FA flows ## Profile config `~/.heroku/credentials` (mode 600): ```ini [default] api_key = HRKU-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx default_app = my-staging-app [work] api_key = HRKU-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx default_app = production-api require_confirm = true # gate every mutation ``` **Get key:** `heroku authorizations:create` (CLI) OR Account Settings → Authorizations. Use **scoped tokens** (read/write/deploy) — avoid global. ## Helpers > Shared profile/INI/`ctt_*` pattern reference: [profiles-and-credentials](../profiles-and-credentials/SKILL.md).