skills.rest
Tashima-Tarsh
Tashima-TarshCOMMUNITY
Explore all skills by this author →
Website𝕏@thenitishkrGitHub

devops-deploy

Validate DISHA production deployments against security, compliance, and CI/CD requirements.

1|Updated Apr 8, 2026
Search Tags:#devops#deployment#infrastructure#ci-cd#security-compliance#disha#runtime-operations
One-click install
npx skills add https://github.com/Tashima-Tarsh/Disha --skill devops-deploy-tashima-tarsh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: devops-deploy
Source: https://github.com/Tashima-Tarsh/Disha/tree/main/.codex/skills/devops-deploy
Command: npx skills add https://github.com/Tashima-Tarsh/Disha --skill devops-deploy-tashima-tarsh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying DISHA, a governed intelligence workbench for public-interest analysis, requires strict adherence to security, compliance, and operational best practices to avoid misconfigurations, security vulnerabilities, or failed releases that break the product's core contract of auditable, evidence-led operation. Manual validation of deployment prerequisites is error-prone and risks missing critical guardrails.

Core Features & Use Cases

  • Deployment Compliance Checklist: Validates all critical production deployment requirements for DISHA, including non-root container execution, health check exposure, and secrets management.
  • CI Pipeline Governance: Ensures CI workflows include mandatory steps like linting, testing, dependency auditing, SAST, and image scanning to catch issues before production.
  • Pre-Deployment Validation: Confirms required production dependencies (Postgres, Redis, configured auth secret) are in place before rollout, and that rollback and promotion processes are documented.
  • Use Case: A DISHA engineering team preparing a v6.6 production release can use this skill to verify all deployment, security, and operational requirements are met, preventing outages or compliance violations.

Quick Start

Use the devops-deploy skill to confirm your upcoming DISHA production deployment meets all security, CI, and runtime prerequisites before release.

Frequently Asked Questions about devops-deploy

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

FAQPage Schema
How do I validate DISHA production deployment prerequisites for CI and security compliance?▼

To validate DISHA production deployment prerequisites, use a compliance checklist to confirm non-root container execution, health check exposure, and secrets management. This prevents misconfigurations and security vulnerabilities before releasing the governed intelligence workbench.

What steps are required for DISHA CI pipeline governance before a production release?▼

Required steps for DISHA CI pipeline governance include integrating mandatory linting, testing, dependency auditing, SAST, and image scanning into workflows. These validations catch security vulnerabilities and compliance issues before production rollout.

Do I need Postgres and Redis configured before DISHA pre-deployment validation?▼

Yes, you need Postgres, Redis, and a configured auth secret in place before DISHA pre-deployment validation. Confirming these production dependencies ensures the runtime infrastructure supports the governed intelligence workbench before rollout.

What is non-root container execution and why is it required for DISHA deployments?▼

Non-root container execution is a security best practice where the container runs applications without root privileges. It is required for DISHA deployments to satisfy strict security and compliance contracts for auditable, evidence-led public-interest analysis operations.

Can I use automated rollback procedures without documenting promotion processes for DISHA?▼

No, DISHA pre-deployment validation requires that both rollback and promotion processes are explicitly documented. Documenting these runtime operations ensures the engineering team maintains auditable compliance during governed intelligence workbench releases.

Why does DISHA deployment require structured logging and CI pipeline auditing?▼

DISHA deployment requires structured logging and CI pipeline auditing to satisfy the product's core contract of auditable, evidence-led operation. These operational best practices ensure runtime infrastructure compliance for public-interest analysis use cases.

Related Skills

Explore More Software Engineering Skills→
habrahgithubhabrahgithub

database

Provision and connect Postgres, Redis, MySQL, or MongoDB databases for Railway projects.

Community
Advanced
a29paula29paul
1

land-and-deploy

Merge approved PRs, wait for CI and deployment pipelines, and verify production canary checks.

Community
Advanced
devkenidevkeni
1

container-security

Scan Docker images, audit Kubernetes clusters, and monitor container runtimes for security weaknesses.

Community
Advanced
aef123aef123

deploy

Deploy Copilot Session Tracker to Azure using Azure CLI and PowerShell.

Community
Advanced