skills.rest
dgmdan
dgmdanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

heroku-cli-investigator

Provides step-by-step Heroku CLI commands to inspect dynos, logs, builds, CI runs, and Postgres health without modifying resources.

Updated Mar 4, 2026
Search Tags:#devops#debugging#troubleshooting#cli#heroku#postgres#dynos
One-click install
npx skills add https://github.com/dgmdan/heroku-cli-investigator-skill --skill heroku-cli-investigator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: heroku-cli-investigator
Source: https://github.com/dgmdan/heroku-cli-investigator-skill/tree/main
Command: npx skills add https://github.com/dgmdan/heroku-cli-investigator-skill --skill heroku-cli-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides step-by-step guidance for using the Heroku CLI to investigate operational incidents related to dynos, logs, releases, builds, CI runs, and Postgres health without making any changes to the Heroku app.

Core Features & Use Cases

  • Dyno & Runtime Inspection: Check live dyno status, stream logs, and run investigative commands in one-off dynos.
  • Database Diagnostics: Inspect Postgres health, query activity, and identify long-running queries.
  • Release & Build Analysis: Review release history, pinpoint build failures, and examine CI run results.
  • Use Case: When a Heroku app deployment fails, use this Skill to inspect the release phase output, check build logs, and examine recent dyno logs to identify the root cause.

Quick Start

Use the heroku-cli-investigator skill to list the live dynos and their states for the app 'my-heroku-app'.

Frequently Asked Questions about heroku-cli-investigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failed Heroku deployment using the CLI?▼

To debug a failed Heroku deployment, inspect the release phase output, check build logs, and examine recent dyno logs to identify the root cause. This provides step-by-step CLI guidance for analyzing failed deploys without modifying resources.

What is the best way to check Heroku dyno status and stream logs?▼

The best way to check Heroku dyno status and stream logs is by running investigative CLI commands to inspect live dynos, view their current states, and tail runtime logs. You can also execute diagnostic commands in one-off dynos.

How do I identify long-running queries in Heroku Postgres?▼

To identify long-running queries in Heroku Postgres, use the CLI to inspect database health, query activity, and pinpoint long-running queries. This diagnostic process helps resolve operational incidents without altering the database.

Do I need a specific Heroku CLI version to investigate builds and CI runs?▼

Yes, you need Heroku CLI version 10.17.0 or higher to investigate builds and CI runs. Optionally, installing the @heroku-cli/heroku-builds plugin provides enhanced capabilities for pinpointing build failures and examining CI results.

Can I use Heroku CLI commands to troubleshoot anomalous CI run results?▼

Yes, you can use Heroku CLI commands to troubleshoot anomalous CI run results by examining CI run outputs and reviewing release history. This allows you to investigate operational incidents and identify anomalies without creating resources.

Related Skills

Explore More Software Engineering Skills→
eymasseymass
1

heroku-observability

Consolidate Heroku logs, dyno status, releases, and metrics for health triage.

Community
Intermediate
edulazaroedulazaro
12

lc:analyze-error

Analyze Laravel stack traces and apply code fixes across controllers, models, and database layers.

Community
Advanced
willyu1007willyu1007

instrument-backend-observability

Instrument backend services with logging, error tracking, metrics, and tracing.

Community
Intermediate
Benmore-StudioBenmore-Studio
1

heroku-cli

Manage Heroku apps, dynos, configs, add-ons, and pipelines via CLI.

Official
Advanced