skills.rest
kaiohenricunha
kaiohenricunhaCOMMUNITY
Explore all skills by this author →
𝕏@kaiohenricunhaGitHub

deploy-status

Compare deployed git SHAs against origin/main across production deploy targets.

Updated Apr 14, 2026
Search Tags:#vercel#drift-detection#incident-response#git-sha#flyio#release-verification#deploy-status
One-click install
npx skills add https://github.com/kaiohenricunha/dotbabel --skill deploy-status-kaiohenricunha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deploy-status
Source: https://github.com/kaiohenricunha/dotbabel/tree/main/plugins/dotbabel/templates/claude/skills/deploy-status
Command: npx skills add https://github.com/kaiohenricunha/dotbabel --skill deploy-status-kaiohenricunha

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Manually tracking which git revisions are deployed across multiple production targets and identifying drift from your main branch is time-consuming and error-prone, especially during incident response or post-deploy verification. This Skill automates that process to give you immediate visibility into your production state.

Core Features & Use Cases

  • Auto-target discovery: Automatically detects Vercel and Fly.io production targets from standard project config files (.vercel/project.json, fly.toml), with support for custom targets via .claude/deploy-targets.json.
  • Drift detection: Compares deployed git SHAs across all targets to origin/main to flag ahead, behind, or unknown drift states.
  • Use cases: Use during post-deploy verification to confirm releases went live, incident response to identify the exact version running in production, and pre-merge release drift checks to catch unplanned production changes.

Quick Start

Use the deploy-status skill to check the current production deploy status and drift against origin/main for all configured targets.

Frequently Asked Questions about deploy-status

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

FAQPage Schema
How do I check if my production deployment has drifted from the main branch?▼

To check production deploy drift, you can compare the deployed git SHAs across your targets against origin/main. This Skill automates that comparison, flagging whether production is ahead, behind, or unknown relative to your main branch.

Does deploy drift detection work with Vercel and Fly.io projects?▼

Yes, deploy drift detection works with Vercel and Fly.io. The Skill auto-discovers production targets from standard project config files like .vercel/project.json and fly.toml, and also supports custom targets via a JSON configuration file.

How do I verify which git commit is currently running in production during an incident?▼

To verify the exact git commit running in production during incident response, use this Skill to instantly show the deployed git SHAs across all configured targets. It identifies the precise version running live without manual checks.

Do I need to configure API keys to check deployment status across multiple targets?▼

No separate API keys are needed to check deployment status. The Skill uses your existing provider CLI authentication state, automatically detecting targets from standard configuration files to compare deployed versions against origin/main.

What is the best way to automate release verification across multiple deploy targets?▼

The best way to automate release verification is comparing deployed git SHAs against origin/main. This Skill exits with distinct codes for in-sync, drifted, and target failure states, allowing you to programmatically confirm releases went live.

Can I add custom deploy targets for drift detection beyond Vercel and Fly.io?▼

Yes, you can add custom deploy targets for drift detection. Beyond auto-discovering Vercel and Fly.io targets, the Skill supports custom production targets configured via the .claude/deploy-targets.json file.

Related Skills

Explore More Software Engineering Skills→
cruzanstxcruzanstx
6

config-reader

Parse daplug configuration from CLAUDE.md blocks and legacy plaintext.

Community
Advanced
EmasoftEmasoft
1

amcos-failure-notification

Identify failure events and route structured alerts through AI Maestro messaging.

Community
Advanced
deveshkumarsdeveshkumars

land-and-deploy

Merge PRs, run CI checks, deploy, and verify production via canary tests.

Community
Advanced
bejranondabejranonda
27

web-validation

Detect JavaScript errors and collect browser diagnostics from web pages.

Community
Advanced