jinn-deploy

Plan and execute deployments with pre-checks, strategies, and rollback procedures.

1|Updated Sep 2, 2019
One-click install
npx skills add https://github.com/hackefeller/hominem --skill jinn-deploy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jinn-deploy
Source: https://github.com/hackefeller/hominem/tree/main/.claude/skills/jinn-deploy
Command: npx skills add https://github.com/hackefeller/hominem --skill jinn-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying to any environment and verifying results requires careful coordination and verification; this Skill provides a structured approach to deployment and post-deployment verification.

Core Features & Use Cases

  • Pre-deployment checklists to ensure tests pass, migrations are reversible, and environment configuration is consistent.
  • Deployment strategies guidance (Blue-Green, Rolling, Canary) with rollback options and failure diagnosis.
  • Post-deployment verification steps, including health checks, error-rate comparison, and log review.
  • When it goes wrong, steps to rollback, preserve evidence, diagnose offline, and re-deploy with fixes.
  • Environment parity and guardrails to prevent drift and ensure repeatable releases.

Quick Start

Follow the pre-deployment checklist, deploy to the target environment, and monitor health checks and logs to confirm a successful rollout.

Frequently Asked Questions about jinn-deploy

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

FAQPage Schema
What's the best way to manage deployment across staging and production environments?

Managing environment deployments requires documented pre-checklists, health checks, and rollback rules. This ensures environment parity, prevents configuration drift, and enables rapid diagnosis of failures during staging or production releases.

How do I execute a canary deployment with rollback procedures?

Canary deployment execution involves following pre-deployment checks, rolling out incrementally, and monitoring health checks and logs. If failures occur, rollback procedures preserve evidence for offline diagnosis before re-deploying with fixes.

What is a pre-deployment checklist for database migrations and environment configuration?

A pre-deployment checklist verifies that tests pass, migrations are reversible, and environment configuration is consistent. This ensures safe, verifiable releases by confirming environment parity before applying any deployment strategy.

Why does post-deployment verification matter after a Blue-Green deployment?

Post-deployment verification matters because it confirms successful Blue-Green rollouts through health checks, error-rate comparison, and log review. Without verification, environment drift or silent failures can compromise production stability.

Does jinn-deploy support Blue-Green and Rolling deployment strategies?

Yes, jinn-deploy supports Blue-Green, Rolling, and Canary deployment strategies. It provides guidance on rollback options and failure diagnosis to ensure safe, verifiable releases across different environments.

When should I rollback a failed production deployment instead of patching forward?

You should rollback a failed production deployment when health checks fail or error rates spike. Rollback procedures preserve evidence for offline diagnosis, allowing you to re-deploy with fixes rather than patching a compromised environment.