Shravan-Amberkar
- 12 skills
- 0 followers
- 20 hours ago last updated
- ▌ Brms Integration · shravan-amberkar bundleHelps engineering teams adopt a BRMS (Business Rules Management System) built on the GoRules Zen Engine — moving hardcoded business logic into versioned, externally-managed decision tables. Five modes — IDENTIFY (scan a codebase for if/elif threshold logic, fee slabs, and rate tiers that belong in rules), BUILD (create a ruleset via guided UI steps or generated JDM JSON), INTEGRATE (drop a typed evaluation-API client into Python/Go/Node code), TROUBLESHOOT (diagnose 400/404/429/500 eval errors), and STATUS (inspect a live ruleset's version, cache, rate limit, and eval count). Trigger on "where can we use BRMS", "add BRMS / rules to this service", "create a rule for", "evaluate ruleset", or "rule evaluation failing".
- ▌ API Design Reviewer · shravan-amberkarUse when designing or reviewing an HTTP/REST or gRPC API and you want it to be consistent, evolvable, and safe before it ships. Reviews resource naming and URL structure, HTTP method/status correctness, pagination and filtering, idempotency of writes, error response shape, versioning strategy, auth and rate limiting, and backward compatibility. Recommends REST for public/partner APIs and gRPC for internal service-to-service. Trigger when the user shares an API spec (OpenAPI/proto), endpoint definitions, or asks to design or review an API contract.
- ▌ Incident Rca Writer · shravan-amberkarUse when an incident has happened and you need to write a clear, blameless root-cause analysis (RCA) or postmortem from logs, metrics, timelines, and notes. Produces a structured document — summary, impact (who/what/how many/how long), detection, timeline, root cause vs contributing factors, resolution, and concrete preventive action items with owners. Distinguishes trigger from root cause and pushes for systemic fixes (monitoring, guardrails, access control) over one-off patches. Trigger when the user asks to write an RCA/postmortem, analyze an outage or incident, or turn incident notes and logs into a report.
- ▌
- ▌
- ▌ Notification Gateway · shravan-amberkar bundleUse to integrate, migrate to, troubleshoot, or check the status of a multi-channel notification gateway (email, SMS, WhatsApp, OTP) without asking the platform team for sample payloads. Five modes auto-detected from the request — SEND (build a ready-to-use curl + code + JSON payload), SETUP (drop a typed client into the project and wire env vars), MIGRATE (convert existing SendGrid/MSG91/Interakt vendor code to the gateway), TROUBLESHOOT (channel-specific failure checklists with the DB/log queries to run), and STATUS (look up delivery by notification id, reference, or batch). Trigger on "send email/SMS/WhatsApp/OTP", "integrate notifications", "migrate sendgrid/msg91/interakt", "notification failed / not received", or "check delivery status".
- ▌ CI Pipeline Generator · shravan-amberkarUse when setting up CI/CD for a service and you want a working pipeline without learning every detail of the CI system. Generates a GitHub Actions workflow and/or a Jenkinsfile tailored to the repo (Go, Python, or Node) covering lint, test with coverage, build, Docker image build and push, and an optional deploy stage. Includes dependency caching, matrix where useful, branch protections, and secret references done safely. Trigger when the user asks to set up CI, add a GitHub Actions workflow or Jenkinsfile, add a build/test/deploy pipeline, or containerize-and-publish on push.
- ▌ Kafka Consumer Builder · shravan-amberkarUse when building a Kafka (or Redpanda) consumer or producer and you want it to be production-safe rather than a naive read loop. Generates an idempotent consumer with explicit offset management, a dedicated consumer group id per service, at-least-once processing with deduplication, bounded retries with backoff, a dead-letter topic (DLQ) for poison messages, graceful rebalance handling, and structured logging/metrics. Also generates idempotent producers with keys for partition affinity. Trigger when the user asks to write/scaffold a Kafka consumer or producer, fix consumer rebalance loops or duplicate processing, or add a DLQ/retry strategy to an existing consumer.
- ▌ Fastapi Service Scaffold · shravan-amberkarUse when creating a new Python FastAPI service or standardizing an existing one to production conventions. Scaffolds a clean layout (app factory, routers, dependencies, settings via pydantic-settings), async SQLAlchemy 2.0 with a session dependency, structured logging, lifespan-based startup/shutdown, health/readiness endpoints, Prometheus metrics, Dockerfile, and tests with pytest + httpx. Trigger when the user asks to create, bootstrap, or scaffold a FastAPI service/API, or to add production structure (config, async DB, health checks, metrics, tests) to existing FastAPI code.
- ▌ Go Microservice Scaffold · shravan-amberkarUse when creating a new Go backend microservice, bootstrapping a Go API, or standardizing an existing Go service to production conventions. Scaffolds an idiomatic layout (cmd/ entrypoint, internal/ packages), 12-factor config loading from env, structured logging with zerolog, context-aware graceful shutdown, liveness/readiness HTTP endpoints, Prometheus /metrics, a multi-stage Dockerfile, and a Makefile. Trigger when the user asks to create, bootstrap, scaffold, or set up a new Go service/API, or to add standard production scaffolding (health checks, metrics, graceful shutdown, Docker) to existing Go code.
- ▌ Postgres Schema Reviewer · shravan-amberkarUse when reviewing PostgreSQL schema changes, migrations, or table designs before they ship. Checks TIMESTAMP vs TIMESTAMPTZ correctness, missing indexes on foreign keys and common query predicates, naming consistency (e.g. request_id vs correlation_id, singular vs plural), nullability and default hygiene, money stored as numeric not float, partitioning candidates for large append-only tables, and unsafe migration operations that take heavy locks (adding NOT NULL with a default on old PG, non-CONCURRENT index creation, rewriting column types). Trigger when the user shares a SQL migration, a CREATE TABLE / ALTER TABLE statement, an ORM model, or asks to review a database schema or migration.
- ▌ Observability Instrumenter · shravan-amberkarUse when a service lacks proper metrics, logs, or traces and you want to add the three pillars of observability without over-instrumenting. Adds Prometheus metrics (RED method - rate, errors, duration), structured logging with correlation/request ids, and OpenTelemetry distributed tracing with context propagation across service and Kafka boundaries. Recommends the key SLI metrics and alert thresholds to watch. Trigger when the user asks to add metrics/logging/tracing, instrument a service, set up Prometheus/Grafana/OpenTelemetry, or debug why they have no visibility into production.