Browse the directory

Source-backed agent for reviewing Cloudflare Workers deployments before production release, covering wrangler config, bindings, routes, secrets, compatibility flags, and rollback plans aligned to official Cloudflare docs.

Expert Wrangler CLI deployment skill for release planning, config review, environment checks, version traffic splits, trigger application, and rollback.

Secure Claude Code hooks in shared repositories: version-control hook configs, code review for PreToolUse and PostToolUse scripts, least-privilege matchers, secret scanning, and rollback when hook behavior changes.

Source-backed agent for live production incident debugging with impact framing, timeline reconstruction, alert/log/trace evidence, rollback options, escalation boundaries, and privacy-safe incident notes.

Source-backed rules for deciding when an AI-assisted code review must escalate high-risk changes to security, infrastructure, data, release, or domain owners before merge.

Source-backed rules for reviewing production database migrations before merge with lock-risk checks, expand-contract rollout, backfill controls, rollback limits, and privacy-safe migration evidence.

Long-term memory MCP server for agents, with URI-addressed memories, namespaces, search, aliases, glossary triggers, a visual dashboard, and reviewable rollback snapshots backed by SQLite or PostgreSQL.

Orchestrate Proxmox VM and LXC lifecycle operations via API with safe sequencing, capacity checks, and rollback-aware automation.

Community reusable agent prompt for migrating teams to Claude Code dynamic workflows using official workflows documentation: audit phases, YAML or config migration steps, validation gates, and rollback planning for large codebase automation.

AppDeploy hosted MCP server for chat-native full-stack web app deployment with templates, QA snapshots, version rollback, and live public URLs from Claude or ChatGPT.

Source-backed agent for reviewing Atlas database schema migrations with migration lint, analyzers, drift detection, CI/CD evidence, dev-database simulation, rollout risk, rollback planning, and production safety gates.

Verify MCP server package provenance before Claude Code installation: registry publisher match, repository ownership, release artifact checksums, maintainer history, and rollback when supply-chain signals fail review.

Pin MCP server package versions before adding them to Claude Code: registry verification, lockfile discipline, npx package pins, supply-chain review, and rollback steps aligned to MCP quickstart and registry documentation.

Checklist for reviewing remote MCP servers before team rollout: OAuth scopes, transport security, tool surface, registry provenance, and rollback.

Source-backed checklist for reviewing Claude Code MCP client configuration before a team rollout, covering scopes, transports, commands, secrets, allowlists, denylists, approvals, and rollback.

A source-backed safety checklist for introducing Claude Code hooks with scoped events, minimal authority, reviewable commands, clear ownership, and a rollback path.