Skip to content

agent readiness score

rzp-slash[bot] edited this page May 6, 2026 · 7 revisions

Agent Readiness Score — razorpay/ifsc-api

Scored by /agent-readiness-score. Band scale: <30 Not Ready | 30–54 Needs Work | 55–79 Assisted | 80+ Ready.

Last scored: 2026-05-06

Pillar Score /Max % Band
Context 4 /14 28.6% Not Ready
Testing 0 /30 0.0% Not Ready
CI/CD 1 /14 7.1% Not Ready
Aggregate 5 /58 8.6% Not Ready

Sub-criterion Breakdown

# Sub-criterion Score Max Key Evidence
C1 Agent-ready plugin outputs 0 6 20 failures, 2 warnings; AGENTS.md and .agents/ both absent
C2 Codebase navigability 4 4 No qualifying subdirectories (≥15 src files); 100% coverage
C3 Context freshness 0 4 No repo-skill docs with frontmatter; Freshness 0/4
T1 (UT) Unit test coverage 0 3 UT: 0% — no Sonar project found for ifsc-api (Ruby/Sinatra, no sonar-project.properties)
T1 (SLIT) SLIT / integration coverage 0 6 SLIT: 0% — not onboarded to MCC; no slit-ifsc-api logs in Coralogix nonprod (30d)
T1 (E2E) E2E coverage 0 5 E2E: 0% — not onboarded to MCC; no e2e-ifsc-api logs in Coralogix nonprod (30d)
T2 API & gRPC contract docs 0 5 Ruby/Sinatra service; no swagger, OpenAPI, or gRPC specs; no buf.yaml or proto files
T3 Devstack v2 readiness 0 5 No dev/ifsc-api/ in kube-manifests; no helmfile.yaml in repo; no v1 or v2 devstack
T4 (Uptime) Devstack deployment SR 0 3 Uptime: no data — kube_deployment_status_replicas_ready{namespace="ifsc-api"} returns empty
T4 (E2E SR) E2E test success rate 0 3 E2E SR: no data (no Argo E2E runs in 7d)
D1 Agent skill coverage in CI 0 4 No .agents/skills/; no agent skills wired in CI workflows
D2 Deployment automation 0 4 Not found in spinacode (no v3/ifsc-api/ folder, no app.json match, no jsonnet match)
D3 CI speed & build hygiene 1 3 p50: ~228s (~3.8 min); uses docker/build-push-action (not razorpay/actions/docker-image-build-push); no Harbor caching; no path filters
D4 Take-it-live config 0 1 take-it-live.yaml absent
D5 Baseline-monitoring 0 2 No relevant metric surfaces detected (Ruby/Sinatra — no goutils/grpcserver); no vajra-iac dashboard; no alert-rules entry

Summary

ifsc-api is a compact Ruby/Sinatra IFSC code lookup service that earns full C2 marks due to its small, flat codebase (no source subdirectory with ≥15 files) requiring no per-directory navigation aids. The Testing pillar is entirely unscored (0/30): the service has no SonarQube project (Ruby, not covered by Razorpay's Go-centric MCC pipeline), no MCC onboarding for SLIT or E2E, and no API contract documentation. CI is naturally fast (~3.8 min p50) but uses the public docker/build-push-action rather than the central razorpay/actions/docker-image-build-push, has no Harbor cache, and no path filters — earning D3=1. The service has no devstack presence (T3=0, T4-Uptime=0) and no Spinnaker pipeline in spinacode (D2=0).

Highest-leverage fixes (in order of impact)

  1. Install the agent-ready plugin and scaffold .agents/skills/repo-skill/ + AGENTS.md + CLAUDE.md → unlocks C1 (up to 6 pts) and C3 (up to 4 pts)
  2. Onboard to devstack v2 — add dev/ifsc-api/ in kube-manifests → unlocks T3 (up to 5 pts) and T4-Uptime (up to 3 pts)
  3. Create a Spinnaker pipeline in spinacode (v3) → unlocks D2 (up to 4 pts)
  4. Add OpenAPI/Swagger spec for the REST endpoints (GET /:code, GET /search, GET /places) → unlocks T2 (up to 4 pts)
  5. Wire agent skills (code-review, pre-mortem) to GitHub Actions → unlocks D1 (up to 4 pts)

Scored from commit c61accb (master). Re-run after changes are pushed.

Clone this wiki locally