Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub j0ruge/skills_commands_manager --plugin deployApply non-obvious session lessons to a target skill in two modes — full (marketplace skill: bumps version, updates CHANGELOG/marketplace.json/README, commits and pushes) or lean (local skill in another repo: edits files + CHANGELOG and commits there, no bump or marketplace changes). Triggers — retrofit, skill-maintenance, session-lessons, lean-retrofit, local-skill.
Self-hosted Zitadel v4 OIDC field guide — 43 documented quirks + working docker-compose, idempotent TypeScript bootstrap, and reset script. High-friction traps: FirstInstance env placement, JWT/JWKS over self-signed HTTPS, TLS-terminating reverse proxy (`--tlsMode external`) and the admin-console `Failed to fetch` mixed-content trap, Login UI v1/v2, v2.66→v4 upgrade, API v1→v2 mapping, silent-renew, 401-storm defenses, smoke-e2e CI. Triggers — zitadel, oidc self-hosted, silent-renew, JWKS, masterkey, v2.66→v4, api v1→v2, login-ui-v2, tlsMode external, console Failed to fetch, mixed content, smoke-e2e CI, Playwright self-signed Zitadel.
GitHub Actions / Docker / GHCR pipeline troubleshooting and config — auto-routes by stack: backend Node (Prisma/Biome) or Django (gunicorn), plus frontend Vite. Deep self-hosted runner runbook (containerized myoung34 + systemd): registration-token chicken-and-egg, ACCESS_TOKEN/PAT migration, deprecated-binary & deleted-registration crashloops, stacked failures, silently-queued deploys. Also GHCR auth/TLS-handshake-timeout, reverse-proxy upstream poisoning, Django ALLOWED_HOSTS healthcheck-400. Triggers — CI/CD, GitHub Actions, GHCR auth, self-hosted runner, runner crashloop, registration token expired, runner version deprecated, compose run orphan, deploy queued, Django gunicorn.
Code review toolkit: automated pre-PR review with severity grading, TOCTOU race condition detection, accessibility checks, data integrity analysis, deterministic hardcoded secrets detection via shell script (passwords, JWT, AWS/GCP/GitHub tokens, PEM keys — GitGuardian-equivalent, applied to CODE/TESTS/CONFIG, with optional ggshield/gitleaks integration when installed), a parallel whole-repo dead-code sweep (unused exports, orphaned files, unreachable code via knip/ts-prune/vulture or grep, with cleanup recommendations), and multi-reviewer PR comment resolver (CodeRabbit, Copilot, Gemini, Codex) with GitHub conversation resolution and model-tier routing for token efficiency. Stack-agnostic with TypeScript/React defaults and dotnet preset for C#/.NET projects.
Interactive setup for Claude Code status line — customize model info, context bar, git branch, cost tracking, and more. Cross-platform: generates Bash (.sh) or PowerShell (.ps1) based on OS.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines, automating quality gates, configuring test runners in CI, or establishing deployment strategies.
DevOps and deployment automation - CI/CD pipelines, zero-downtime deployments - 1 skill, 2 commands, 2 agents
Use this agent when setting up CI/CD pipelines, configuring Docker containers, deploying applications to cloud platforms, setting up Kubernetes clusters, implementing infrastructure as code, or automating deployment workflows. Examples: <example>Context: User is setting up a new project and needs deployment automation. user: "I've built a FastAPI application and need to deploy it to production with proper CI/CD" assistant: "I'll use the deployment-engineer agent to set up a complete deployment pipeline with Docker, GitHub Actions, and production-ready configurations."</example> <example>Context: User mentions containerization or deployment issues. user: "Our deployment process is manual and error-prone. We need to automate it." assistant: "Let me use the deployment-engineer agent to design an automated CI/CD pipeline that eliminates manual steps and ensures reliable deployments."</example>
Deployment automation with Dockerfile generation, CI/CD pipelines, and infrastructure as code
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
Build CI/CD pipelines for GitHub Actions, GitLab CI, Jenkins, and more