check-deploy-status

Retrieve recent AWS Amplify deployment job summaries across specified profiles and branches.

108|19|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/minorun365/marp-agent --skill check-deploy-status-minorun365
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-deploy-status
Source: https://github.com/minorun365/marp-agent/tree/main/.agents/skills/check-deploy-status
Command: npx skills add https://github.com/minorun365/marp-agent --skill check-deploy-status-minorun365

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the manual and error-prone process of checking AWS Amplify deployment status across multiple environments and branches, consolidating recent job summaries and elapsed times so you can quickly identify failing or long-running builds.

Core Features & Use Cases

  • Retrieves all branches for specified Amplify apps and lists up to the five most recent jobs per branch.
  • Computes human-readable durations for running and completed jobs and maps Amplify statuses to clear emoji indicators for quick triage.
  • Handles AWS SSO session validation and instructs when to re-authenticate, making it suitable for developer and DevOps workflows that monitor CI/CD health across personal and corporate AWS profiles.
  • Use case: an engineer verifying the last five deploys for each branch in both personal and corporate Amplify apps to find recent failures or unusually long builds.

Quick Start

Run the Amplify deployment check for both sandbox and kag-sandbox AWS profiles and output each branch's latest five job statuses with human-readable durations.

Frequently Asked Questions about check-deploy-status

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

FAQPage Schema
How do I check AWS Amplify deployment status across multiple branches?

Check AWS Amplify deployment status by retrieving recent job summaries for all branches across specified AWS profiles. The tool lists up to five recent jobs per branch, mapping statuses to emoji indicators and computing human-readable durations to help you quickly triage failing or long-running builds.

What is the best way to monitor Amplify CI/CD health for recent build failures?

Monitoring Amplify CI/CD health involves retrieving recent job summaries across specified apps and AWS profiles, displaying up to five recent jobs per branch with mapped statuses, truncated commit messages, and elapsed or total durations in JST to identify failures or unusually long builds.

Do I need AWS CLI SSO authentication to inspect Amplify branch deployments?

Yes, AWS CLI SSO authentication is required to inspect Amplify branch deployments. The tool validates your SSO session and instructs you when to re-authenticate, making it suitable for developer and DevOps workflows monitoring CI/CD health across personal and corporate AWS profiles.

Can I view elapsed durations for running Amplify jobs in JST?

Yes, you can view elapsed durations for running Amplify jobs in JST. The tool computes human-readable durations for both running and completed jobs, providing elapsed or total durations alongside job IDs, mapped statuses, and truncated commit messages.

How many recent deployment jobs can I list for each Amplify branch?

You can list up to five recent deployment jobs for each Amplify branch. The tool retrieves all branches for specified Amplify apps and outputs the five most recent job summaries per branch, including job IDs, statuses, and durations.

Why does my Amplify deployment status check fail to retrieve job summaries?

Your Amplify deployment status check may fail if your AWS CLI SSO session has expired. The tool requires active AWS SSO authentication to access specified profiles; it validates the session and instructs you to re-authenticate when access is denied.