I just launched πππ―ππ©π¬ ππ¨πππ¨π« a Codex plugin built for DevOps, SRE, platform, and cloud engineers.
DevOps Doctor is a Codex plugin that helps investigate production issues across GitLab, AWS, infrastructure, logs, and recent changes, then reports what failed, why it failed, and the safest fix with validation and rollback steps.
Production issues are rarely solved by quick guesses.
They need evidence.
They need context.
They need safe rollout thinking.
They need rollback plans.
They need context.
They need safe rollout thinking.
They need rollback plans.
That is why I built πππ―ππ©π¬ ππ¨πππ¨π«.
It helps Codex work more like a careful DevOps/SRE pair when dealing with real infrastructure, CI/CD, deployments, incidents, and production risk.
What it can help with:
β
GitLab CI/CD failure investigation
β GitLab MR review for DevOps risk
β AWS deployment debugging
β ECS/Fargate troubleshooting
β Terraform plan review
β Infrastructure drift checks
β Cost optimization review
β Security drift review
β Observability and incident investigation
β Rollback planning
β Docker, Kubernetes, repo, and config review
β GitLab MR review for DevOps risk
β AWS deployment debugging
β ECS/Fargate troubleshooting
β Terraform plan review
β Infrastructure drift checks
β Cost optimization review
β Security drift review
β Observability and incident investigation
β Rollback planning
β Docker, Kubernetes, repo, and config review
How it works:
- You give Codex a DevOps problem.
- DevOps Doctor guides Codex to collect the right evidence.
- It reviews repo files, pipelines, Terraform, Docker, AWS context, logs, and CLI output where available.
- It avoids guessing production state.
- It clearly reports missing tools, permissions, or evidence.
- It suggests the smallest safe fix.
- It includes validation and rollback steps.
Example prompts:
βInvestigate this failed GitLab pipeline.β
βReview this Terraform plan for production risk.β
βDebug why my ECS/Fargate deployment is unhealthy.β
βCheck this MR for CI/CD, Docker, and infrastructure risk.β
βPlan a safe rollback for this deployment.β
In DevOps and SRE, the best answer is not always the fastest one.
The best answer is the one that is:
β
evidence-based
β safe to apply
β easy to validate
β easy to roll back
β clear enough for production decisions
β safe to apply
β easy to validate
β easy to roll back
β clear enough for production decisions
πππ―ππ©π¬ ππ¨πππ¨π« is my attempt to bring that production-ready mindset into Codex as reusable DevOps workflows.
GitHub: https://github.com/mojahid0862/devops-doctor
Install:
πππππ‘ ππππππ πππππππππππ πππ πππππ://ππππππ.πππ/ππππππππΆπΎπΌπΈ/ππππππ-ππππππ.πππ --πππ ππππ
πππππ‘ ππππππ πππ ππππππ-ππππππ@ππππππ-ππππππ
Then start a new Codex thread and use DevOps Doctor.
This is the first public version, and Iβll keep improving it around real cloud, CI/CD, cost, security, observability, and incident-response workflows.
If you work in DevOps, SRE, platform engineering, cloud, or CI/CD, Iβd love your feedback.
#DevOps #SRE #PlatformEngineering #CloudEngineering #AWS #GitLab #Terraform #Kubernetes #Docker #CICD #Observability #IncidentResponse #InfrastructureAsCode #AI #Codex
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article