NotHarshhaa
- 15 skills
- 0 followers
- 13 hours ago last updated
- ▌ Cost · notharshhaa bundleIdentify cloud cost optimization opportunities as a senior FinOps/cloud engineer across compute, storage, networking, and managed services, then produce a prioritized, evidence-based findings table and self-contained remediation plans that cut waste without hurting reliability. Strictly read-only — never resizes, deletes, or modifies resources. Use when asked to reduce cloud spend, find waste, right-size infrastructure, or review cost efficiency of IaC or a live account.
- ▌ Audit · notharshhaa bundlePerform a broad infrastructure and DevOps audit as a senior platform engineer, across reliability, security, cost, observability, and operability, then produce a prioritized, evidence-based findings table and self-contained remediation plans for other agents to execute. Strictly read-only — never applies changes. Use when asked to audit infrastructure, assess DevOps maturity, do a general health check across a repo or environment, or when the specific problem area is unknown and you need to survey everything first.
- ▌ Runbook · notharshhaa bundleWrite or audit operational runbooks as a senior SRE — one document per failure mode, with detection signal, triage decision tree, verified read-only diagnostics, mitigation with rollback, escalation path, and verification — grounded in the real repo, alerts, and dashboards rather than generic advice. Strictly read-only on systems — it drafts documents under runbooks/ and never executes a mitigation itself. Use when asked to write a runbook or on-call playbook, document a failure mode or recovery procedure, close a "no runbook for this alert" gap, or review existing runbooks for staleness and accuracy.
- ▌ Incident · notharshhaa bundleInvestigate a production incident as a senior SRE and produce a hypothesis-driven, evidence-logged investigation document plus recommended (never auto-applied) mitigations and durable follow-up plans. Strictly read-only — runs diagnostic and read-only commands only, never restarts, scales, rolls back, or changes anything itself. Use when asked to investigate an outage, degradation, error spike, latency regression, failed deploy, or any "why is production broken" question, or to run a blameless post-incident analysis.
- ▌ DB Review · notharshhaa bundleReview database operations and schema-change safety as a senior database reliability engineer — migrations, locking and blocking risk, connection pooling, indexing, replication, PITR, and production data-access paths — then produce an evidence-based findings table and self-contained remediation plans. Strictly read-only — never runs a migration, DDL, DML, kill, failover, or any statement that changes data or schema. Use when asked to review a database migration for safety, assess whether a schema change can be deployed with zero downtime, diagnose connection-pool exhaustion or slow queries from config, or review database reliability and operational posture.
- ▌ Dr Review · notharshhaa bundleReview backup, restore, and disaster-recovery readiness as a senior SRE — whether backups exist, are recoverable, meet the stated RTO/RPO, survive deletion or ransomware, and whether failover has actually been tested — then produce an evidence-based findings table and self-contained remediation plans. Strictly read-only — never triggers a restore, failover, snapshot deletion, or any change. Use when asked about backups, restore testing, RTO/RPO, data-loss risk, multi-region or multi-AZ failover, business continuity, or "what happens if this database/region/account is lost".
- ▌ K8S Review · notharshhaa bundleReview Kubernetes manifests, Helm charts, Kustomize overlays, and live workloads as a senior Kubernetes engineer, then produce a prioritized, evidence-based findings table and self-contained remediation plans. Strictly read-only — never applies, scales, deletes, or patches anything. Use when asked to review Kubernetes YAML, Helm charts, or cluster workloads for reliability, security, resource management, or best-practice compliance.
- ▌ Docker Review · notharshhaa bundleReview Dockerfiles, container images, and Compose files as a senior container engineer, then produce a prioritized, evidence-based findings table and self-contained remediation plans covering image size, build speed, security, and correctness. Strictly read-only — inspects and scans only, never builds-and-pushes or edits. Use when asked to review Dockerfiles, container build setups, image layering, or container security and best practices.
- ▌ Gitops Review · notharshhaa bundleReview GitOps delivery pipelines, reconciliation status, and repository-to-cluster sync safety as a senior GitOps / platform engineer across ArgoCD, Flux, and Kubernetes controllers, then produce an evidence-based findings table and self-contained remediation plans. Strictly read-only — inspects apps, diffs, and health only, never triggers syncs, overrides drift, or mutates resources. Use when asked to review ArgoCD or Flux setups, diagnose OutOfSync apps, audit automated sync/prune policies, inspect sync-wave ordering, or fix secret operator reconciliation loops.
- ▌ Observability · notharshhaa bundleReview monitoring, metrics, logging, tracing, dashboards, and alerting as a senior SRE, then produce a prioritized, evidence-based findings table and self-contained remediation plans that close observability gaps and reduce alert noise. Strictly read-only — never edits dashboards, alert rules, or config. Use when asked to review observability posture, assess whether incidents would be detected, evaluate SLOs/alerts, or fix noisy or missing monitoring.
- ▌ Upgrade Review · notharshhaa bundleAudit infrastructure for deprecated APIs, breaking changes, and End-of-Life (EOL) runtimes as a senior platform engineer before upgrading Kubernetes clusters, Terraform providers, or language runtimes, then produce an evidence-based upgrade readiness report and sequenced, zero-downtime remediation plans. Strictly read-only — scans and plans only, never initiates an upgrade or modifies state. Use when asked to plan a Kubernetes cluster upgrade, check for deprecated Kubernetes APIs or Helm charts, review Terraform provider major-version migrations, assess upgrade risks, or plan runtime EOL migrations.
- ▌ Pipeline Review · notharshhaa bundleReview CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure Pipelines, etc.) as a senior release engineer, then produce a prioritized, evidence-based findings table and self-contained remediation plans covering reliability, speed, security, and correctness. Strictly read-only — never triggers, cancels, or edits pipelines. Use when asked to review CI/CD configuration for flakiness, slow builds, insecure secrets handling, missing gates, or supply-chain risk.
- ▌ Security Review · notharshhaa bundleIdentify security risks and infrastructure misconfigurations as a senior security/DevSecOps engineer across IaC, Kubernetes, containers, pipelines, cloud config, and secrets handling, then produce a prioritized, evidence-based findings table and self-contained remediation plans. Strictly read-only and defensive — never exploits, never applies changes, never reproduces secret values. Use when asked to review infrastructure security posture, find misconfigurations, assess IAM/network/secrets exposure, or harden a deployment.
- ▌ Terraform Review · notharshhaa bundleReview Terraform (or OpenTofu) code and infrastructure design as a senior cloud/IaC engineer, then produce a prioritized, evidence-based findings table and self-contained remediation plans. Strictly read-only — runs plan/validate only, never apply, destroy, or state changes. Use when asked to review Terraform modules, root configurations, state management, or IaC design for correctness, security, cost, and maintainability.
- ▌ Release Readiness · notharshhaa bundleValidate production deployment readiness as a senior release manager/SRE by checking whether a service or release meets reliability, security, observability, rollback, and operational bars before it ships, then produce a go/no-go assessment with an evidence-based gap list and self-contained remediation plans for blockers. Strictly read-only — never deploys, promotes, or changes anything. Use when asked whether something is ready to go to production, to run a pre-launch/pre-deploy checklist, or to gate a release.