Skip to content
Skills Library
DevOps & cloud · Analysis

deploy-status-report

/deploy-status-report

Use when checking deployment status, Spinnaker deploys, canary results, what's deployed, pending rollouts, or generating a deployment report. Trigger phrases: deploy status, what's deployed, spinnaker status, canary results, deployment report, rollout status.

Author
npow ↗
Licence
Apache-2.0
Last repository change
20.08.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.08.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when checking deployment status, Spinnaker deploys, canary results, what's deployed, pending rollouts, or generating a deployment report. Trigger phrases: deploy status, what's deployed, spinnaker status, canary results, deployment report, rollout status.

Original author description

Use when checking deployment status, Spinnaker deploys, canary results, what's deployed, pending rollouts, or generating a deployment report. Trigger phrases: deploy status, what's deployed, spinnaker status, canary results, deployment report, rollout status.

How it works

  1. Configuration
  2. Arguments
  3. Workflow
  4. Design Principles
  5. Golden Rules
  6. Anti-Rationalization Counter-Table
  7. Termination Labels
  8. Self-Review Checklist
Original SKILL.md headings · 103 lines, 777 words
SKILL.md preview
---
name: deploy-status-report
description: "Use when checking deployment status, Spinnaker deploys, canary results, what's deployed, pending rollouts, or generating a deployment report. Trigger phrases: deploy status, what's deployed, spinnaker status, canary results, deployment report, rollout status."

category: report
capabilities: [static-analysis]
input_types: [repo]
output_types: [design-spec, report]
complexity: moderate
cost_profile: low
maturity: beta
metadata_source: inferred
---

# Deployment Status Report

Produce an actionable report on Spinnaker deployment state using Delivery MCP tools.

## Configuration

See [`_shared/report-config.md`](../_shared/report-config.md) for the standard config resolution pattern.

**Config schema** (`~/.claude/skills/deploy-status-report/config.json`):
- `apps`: list of Spinnaker application name strings
- `lookback_days`: number (default: 7)

**Required scope:** at least one `apps` entry.

## Arguments

- **apps**: list of Spinnaker application names to check
- **lookback_days**: how far back to check executions (default: match your cadence — 1 for daily, 7 for weekly)

## Workflow

1. **Check Managed Delivery status.** For each app, invoke `delivery:delivery-managed-delivery` to get current deployed versions, pending deploys, constraint state (canary, deploy windows, depends-on), and verification results.

2. **Check recent pipeline executions.** For each app, invoke `delivery:delivery-spinnaker` to get recent pipeline execution history. Note any failed executions.

3. **Get canary details for failures.** For any app with a failed canary constraint, invoke `delivery:delivery-managed-delivery-canary` to get per-interval scores and region breakdown.

4. **Analyze failed executions.** For any failed pipeline execution, invoke `delivery:delivery-execution-failure-analysis` with the execution ID to get EFA results.

5. **Generate report.** Output markdown:

```
## Deployment Status Report — {date}
Period: last {lookback_days} days | Apps checked: {N}

### Summary
- Apps with blocked deploys: {count} | Failed canaries: {count} | Successful deploys: {count}

### Blocked Deploys
(For each: app, what's blocked, constraint type, details, Chap URL)

### Failed Canaries
(For each: app, canary score, failing metrics, analysis ID, Chap URL)

### Failed Pipeline Executions
(For each: app, pipeline name, failure reason from EFA, execution link)

### Successfully Deployed
(For each: app, current version, deploy time, regions)

### Pending
(For each: app, pending version, waiting on what constraint)
```

6. **Deliver as HTML.** Follow the shared HTML delivery pattern in [`_shared/html-delivery.md`](../_shared/html-delivery.md). Report name: `deploy-status`. TLDR includes apps checked, blocked deploys count, and failed canaries count.

7. **Terminate.** Report is complete when all sections are populated.

## Design Principles

1. **Team-level only.** Aggregate to team level — it is the right granularity for a periodic digest. Individual-level detail (commits per person, PR count per author) is too noisy for a team report.
2. **Deterministic math first, LLM narrates only.** All classification (severity, flaky vs broken, pass/fail) must be computed deterministically from data. The LLM writes prose around the numbers but never assigns severity or makes classification judgments.
3. **Pair metrics with counter-metrics.** Never report velocity without stability. If showing deploy frequency, also show change failure rate. If showing PR throughput, also show rework rate.

## Golden Rules

1. **Check Managed Delivery first.** It gives the current state of what's deployed and what's pending. Pipeline history is supplementary.
2. **Always get canary details for failed canaries.** "Canary failed" without scores is not actionable. Call the canary skill.
3. **Always get EFA for failed executions.** "Pipeline failed" without EFA diagnosis is not actionable.
4. **Include Chap URLs.** Every blocked deploy and failed canary includes the Chap URL from the API response.
5. **Check ALL apps, not a sample.** Every configured app gets checked every run.
6. **Blocked deploys are the highest priority.** They represent work that's stuck. Surface them first.

## Anti-Rationalization Counter-Table

| Excuse | Reality |
|---|---|
| "The deploy looks fine, I'll skip the canary details." | If a canary failed or is pending, get the scores. "Looks fine" is not evidence. |
| "Pipeline failed but I didn't run EFA because the status is clear." | EFA gives the root cause. Status gives the outcome. You need both. |
| "I checked the main app, the others are probably fine." | Check ALL configured apps. A blocked deploy on a secondary app is still a blocked deploy. |
| "No Chap URL in the response, I'll skip the link." | Chap URLs are in the delivery tool responses. Look for them in the constraint and verification fields. |

## Termination Labels

| Label | Meaning |
|---|---|
| `report_complete` | All apps checked, blocked deploys detailed, canary scores included |
| `report_partial` | Some apps checked but errors prevented full coverage |
| `no_apps_configured` | No apps specified — need config.json or user input |
| `api_error` | Spinnaker/Delivery API unreachable |

## Self-Review Checklist

- [ ] All configured apps were checked
- [ ] Failed canaries have per-interval scores and Chap URLs
- [ ] Failed executions have EFA analysis
- [ ] Blocked deploys section appears first after summary
- [ ] Chap URLs present for all blocked/failed items
- [ ] Report has date header and app list noted
- [ ] HTML version uploaded to S3 with commuter link (unless `--no-html` or upload failed with noted fallback)
- [ ] Slack/chat delivery uses TLDR + link, not the full report

Versions

The database has no other skills named deploy-status-report.

Database snapshot: 13.11.2026 · package version 331ff2ac45cc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100canary-deployment-setup
    Configure canary deployment setup operations. Auto-activating skill for ML Deployment. Triggers on: canary deployment setup, canary deployment setup Part of the ML Deployment skill category. Use when deploying applications or services. Trigger with phrases like "canary…
  • 100ops-deploy
    OPS on-demand: This skill should be used when the user asks to \"deploy status\", \"what is in…
  • 100nacl-tl-deploy
    Monitor CI/CD deployment results, run health checks, and report deployment evidence for NaCl TL tasks. Use when checking deploy status, verifying a staging or production deployment, or when the user says `/nacl-tl-deploy`.
  • 100deployment-readiness
    Assess deployment readiness via Harness MCP. Run pre-deployment readiness checks with go/no-go recommendations, analyze environment drift between source and target environments, and provide data-driven canary rollout decisions. Use when asked to check if a service is ready to…
  • 100k8s-deploy
    Deploy and manage Kubernetes workloads with progressive delivery. Use for deployments, rollouts, blue-green, canary releases, scaling, and release management.
  • 84orchestrate-deployment
    Orchestrate deployment pipelines and infrastructure. Use when user says "deploy to staging", "set up CI/CD for this project", "configure deployment pipeline", "deploy to production with canary", or "rollback the last deployment".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.