What is deploy-check?

A pre-deployment check for code changes that reviews the changes, identifies affected Rootly services, and checks for active incidents before deployment.

Use it before deploying to inspect the current diff, branch, recent commits, related services, and incident status.

It helps reveal operational risks that may make a deployment unsafe, such as an ongoing incident affecting the same service.

deploy-check — Skill for Claude Code by Rootly-AI-Labs: A pre-deployment check for code changes that reviews the…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/rootly-ai-labs/rootly-claude-plugin/deploy-check

Any agent

npx skills add Rootly-AI-Labs/rootly-claude-plugin --skill deploy-check

Clone the repo

git clone --depth 1 https://github.com/Rootly-AI-Labs/rootly-claude-plugin

Made for: Claude Code.

Or install rootly-claude-plugin, the plugin that ships this one along with the rest of its 18 skills, 3 agents, 2 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/deploy-check.svg)](https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/deploy-check)

Your own site

<a href="https://agentmods.dev/skills/rootly-ai-labs/rootly-claude-plugin/deploy-check"><img src="https://agentmods.dev/badge/skills/rootly-ai-labs/rootly-claude-plugin/deploy-check.svg" alt="Measured on agentmods" height="20"></a>

Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 881 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00041	$0.00881
Opus 5	$0.00020	$0.00441
Sonnet 5	$0.00008	$0.00176
Haiku 4.5	$0.00004	$0.00088

Measured 6d ago against content hash f93756bd8d26, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

deploy-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/deploy-check/SKILL.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pre-Deploy Safety Check (experimental)

Experimental: this skill uses context: fork to delegate to the deploy-guardian agent. In some Claude Code contexts the forked subagent does not inherit the plugin's MCP tools. If the agent reports MCP tools unavailable, run /rootly:status to manually check active incidents before deploying.

You are evaluating whether it is safe to deploy the current code changes. Follow this workflow carefully.

Current changes

!git diff --stat HEAD

Current branch

!git branch --show-current

Recent commits

!git log --oneline -5

Workflow

1. Assess Changes

Review the git diff output above. If the diff is empty (no changes), report "No changes to evaluate -- working tree is clean" and stop.

Identify which files and components are affected by the changes.

2. Resolve Affected Services

Determine which Rootly service(s) these changes map to, using this resolution chain (in priority order):

Check .claude/rootly-config.json in the project root -- if it exists, use the services field
Match repo name: Use the git repo name (from basename $(git rev-parse --show-toplevel)) to search for matching Rootly services via mcp__rootly__search_incidents
Ask the user: If neither method works, ask which service(s) this repo maps to

3. Search Incident History

Call mcp__rootly__search_incidents for the identified services, looking at the last 90 days. Note any patterns in frequency, severity, or root causes.

4. Find Related Incidents

Call mcp__rootly__find_related_incidents with a summary of the current changes (based on the diff). This uses TF-IDF similarity matching to find historically similar incidents.

If results have confidence scores below 0.3, flag them as low confidence and note that manual review may be needed.

5. Check Active Incidents

Call mcp__rootly__search_incidents filtered to active (started) status for the affected services. Pay special attention to P1/P2 (critical/high severity) incidents.

Read the full file on GitHub · 99 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 99 lines · 41 tokens per session scan A f93756bd8d26

Subscribe to this mod's changes

deploy-check is a skill published in the GitHub repository Rootly-AI-Labs/rootly-claude-plugin (1 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 881 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

CI and CD DevOps and cloud

import-prom-rule

Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…

ccfos/nightingale · 125 tokens

azsdk-common-pipeline-analysis

Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…

Azure/azure-sdk-for-net · 192 tokens

configure-env-variables

Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…

microsoft/power-platform-skills · 119 tokens

deploy-check