AM

Amjith Titus

@amjithtitus09

Software Developer

Software developer focused on building scalable systems, writing clean, maintainable code, and contributing to strong, collaborative teams.

Total Points
3113

All time

Total Activities
1773

All time

Activity Types
8

Different types

Activity Overview

865 contributions in the last year

Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Mon
Wed
Fri
Less
More
Review Champion - bronze

Review Champion

Awarded for consistent code review participation

1 / 4 tiers earned

bronze
bronze

4 days of reviews

silver
silver

8 days of reviews

gold
gold

16 days of reviews

platinum
platinum

32 days of reviews

PR Consistency - bronze

PR Consistency

Awarded for maintaining a consistent pull request contribution streak

1 / 4 tiers earned

bronze
bronze

4 day PR streak

silver
silver

8 day PR streak

gold
gold

16 day PR streak

platinum
platinum

32 day PR streak

Points Milestone - gold

Points Milestone

Awarded for reaching points milestones

3 / 3 tiers earned

bronze
bronze

100+ points

silver
silver

500+ points

gold
gold

1,000+ points

Activity Milestone - platinum

Activity Milestone

Awarded for reaching activity count milestones

4 / 4 tiers earned

bronze
bronze

10+ activities

silver
silver

50+ activities

gold
gold

100+ activities

platinum
platinum

500+ activities

Consistency Champion - bronze

Consistency Champion

Awarded for maintaining activity streaks

1 / 3 tiers earned

bronze
bronze

7 day streak

silver
silver

14 day streak

gold
gold

30 day streak

Activity Breakdown

1459 total activities · 3113 total points

Commit Created
677 (46.4%)·1306 pts
PR Merged
156 (10.7%)·780 pts
PR Reviewed
378 (25.9%)·754 pts
PR Opened
177 (12.1%)·177 pts
Issue Opened
25 (1.7%)·50 pts
Issue Assigned
46 (3.2%)·46 pts
1459
Total Activities
3113
Total Points
6
Activity Types
2.1
Avg Points/Activity
Activity Timeline

81 of 1773 activities· 1 of 25 months

August 202681 activities

PR Merged+5
Consolidate agentic PR reviewers and auto-retry transient 429 failures
Commit Created+2
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743) Co-authored-by: carefe-bot Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commit Created
Consolidate agentic PR reviewers and auto-retry transient 429 failures (#16743)
Commented
PR Opened+1
Consolidate agentic PR reviewers and auto-retry transient 429 failures
PR Reviewed+2
[ENG-950] Skip setting `dispense_status` when creating medication requests
PR Reviewed+2
Fix CARE PR Reviewer workflow (copilot CLI ENOENT) by recompiling
Commented
PR Opened+1
Fix expiring-items note: deliveries are filtered to completed only
PR Merged+5
Fix analytics-review pre-steps: survive Actions' bash -e; JIRA cloudId recovery via _edge/tenant_info
Commit Created+2
Fix pre-steps: survive Actions' bash -e; JIRA recovery via _edge/tenant_info (#153) Item 1 (highest severity): GitHub Actions invokes run: steps as `bash -e {0}`, so errexit is inherited — `set -uo pipefail` does NOT clear it, only an explicit `set +e` does. The KEY extraction pipeline (grep exits 1 on branches without ENG-nnn) therefore killed the "never fails" JIRA step before its no_ticket fallback could run, hard-failing the agent job for every non-ENG-branch PR (observed in run 32017183079 on PR #152). Fix: explicit `set +e` in the JIRA and lint steps with a comment citing the run, `|| true` on the grep pipeline as belt-and-braces, and an audit of all pre-steps (the resolve and skill-move steps stay deliberately strict). Reproduced locally under `bash -e`: main's version exits 1, this version exits 0 and writes the marker. Item 2: the two-URL rule is now empirically confirmed (scoped API tokens are ignored entirely on *.atlassian.net — anonymous and authenticated requests return identical status codes). Replace the accessible-resources probe (OAuth-Bearer-only; returns 401 uniformly for no-auth/bogus-basic/bogus-bearer, so its 401 says nothing about credentials) with the public, unauthenticated GET /_edge/tenant_info for cloudId discovery, and auto-retry via https://api.atlassian.com/ex/jira/. Remove the now unused .github/scripts/jira_sites.py. Item 3: carry forward the hedged diagnostics from orphaned commit c75b882 (pushed after the #152 squash-merge), now decisive where the evidence allows: when the configured host is *.atlassian.net, the marker recommends the ex/jira form outright; arms stay hedged only where JIRA's 404-for-unviewable behaviour makes causes genuinely indistinguishable. README: add the _edge/tenant_info cloudId discovery command. Recompiled with gh-aw v0.86.2 (0 errors, 0 warnings). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
PR Opened+1
Fix analytics-review pre-steps: survive Actions' bash -e; JIRA cloudId recovery via _edge/tenant_info
Commit Created
Fix pre-steps: survive Actions' bash -e; JIRA recovery via _edge/tenant_info
Commit Created
JIRA diagnostics: hedge as likely causes, add two-URL mismatch hint to inconclusive arms
PR Merged+5
Fix analytics-review on workflow_dispatch: pass resolved PR context to the agent
Commit Created+2
Fix analytics-review on workflow_dispatch: pass resolved PR context to the agent (#152) * Fix analytics-review on workflow_dispatch: pass resolved PR context to the agent Dry-run 32015295640 (PR #146) went green end-to-end after the v0.86.2 recompile, but the agent posted nothing: the resolve pre-step's AW_PR_NUMBER/AW_HEAD_REF land in step env only, which never reaches the agent sandbox, and on workflow_dispatch the event payload has no PR object. The agent concluded "no associated pull request ... nothing to review" and noop'd. Fix 1: the resolve step (now id: resolve_pr) also writes step outputs and /tmp/gh-aw/context/run-context.md — the context dir is the one channel proven to reach the agent (it read jira-ticket.md in the same run). The prompt body names run-context.md as the source of truth for PR identity, treats a dispatch run with a resolved PR as a normal review, and reserves noop for runs where no PR resolves at all. (${{ steps.* }} interpolation into the body cannot work: the prompt is rendered in the activation job, the steps run in the agent job.) Fix 2: the same run showed "JIRA returned HTTP 404 for ENG-909" — ambiguous, since JIRA answers 404 for missing ticket, missing project permission, AND bad credentials. On any non-200 the step now probes /rest/api/3/myself and writes an auth diagnosis into the marker (credentials rejected vs authenticated-but-cannot-see vs unreachable), reporting HTTP codes only, never credential values. Still never fails the job. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> * JIRA step: support scoped Atlassian tokens (accessible-resources probe + auto-recovery) Root cause of the ENG-909 404: JIRA_API_TOKEN is a scoped Atlassian API token, and scoped tokens must target https://api.atlassian.com/ex/jira/ instead of https://.atlassian.net. Atlassian answers 404 (not 403) when a scoped token hits the site-host form, which mimics a missing issue. - Replace the /rest/api/3/myself probe (not callable with granular read:issue scopes -> would false-report valid credentials as broken) with GET https://api.atlassian.com/oauth/token/accessible-resources, which works for both token types and returns each site's cloudId. - Auto-recovery: when the issue fetch fails and the probe can resolve a cloudId (configured URL matches a site, cloudId embedded in an ex/jira URL, or single-site token), retry via the scoped-token endpoint - so either token type works with either JIRA_BASE_URL form. - Self-diagnosing markers on hard failure: credentials rejected (401/403, mentions <=365-day scoped-token expiry), base URL matches none of the token's sites (lists reachable site URLs + cloudIds and the exact value to set), ticket not visible/nonexistent (tried both endpoints), or api.atlassian.com unreachable. HTTP codes, site URLs and cloudIds only; never credential values. - Comments fetch now uses the possibly-recovered base URL. - README: JIRA_BASE_URL form guidance per token type. - New helper .github/scripts/jira_sites.py (cloud-id resolution + site summary; always exits 0). All six failure/recovery branches exercised locally against a mock Atlassian server using the step script extracted verbatim from the workflow; every path exits 0 and writes the marker. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Commit Created
Fix analytics-review on workflow_dispatch: pass resolved PR context to the agent (#152)
Commit Created
JIRA step: support scoped Atlassian tokens (accessible-resources probe + auto-recovery)
PR Opened+1
Fix analytics-review on workflow_dispatch: pass resolved PR context to the agent
Commit Created
Fix analytics-review on workflow_dispatch: pass resolved PR context to the agent
PR Merged+5
Recompile analytics-review with gh-aw v0.86.2 (fixes Copilot CLI ENOENT on toolcache hit)
Commit Created+2
Recompile analytics-review with gh-aw v0.86.2 (fixes Copilot CLI ENOENT on toolcache hit) (#151) First workflow_dispatch dry-run (run 32010839654, PR #146) failed at "Execute GitHub Copilot CLI" with `spawn /usr/local/bin/copilot ENOENT`: the v0.85.4 harness hardcoded /usr/local/bin/copilot, but the install step hit the runner toolcache (/opt/hostedtoolcache/copilot-cli) and only appended to GITHUB_PATH. Known upstream bug, fixed in gh-aw v0.86.2 (github/gh-aw#52464): the execute step now resolves the binary via `command -v copilot` and stages it to ${RUNNER_TEMP}/gh-aw/bin/copilot before invoking the harness. Generated files only — source .md workflow/agent files unchanged (frontmatter/body hashes identical in the lock metadata). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
PR Opened+1
Recompile analytics-review with gh-aw v0.86.2 (fixes Copilot CLI ENOENT on toolcache hit)
Commit Created
Recompile analytics-review with gh-aw v0.86.2 (fixes Copilot CLI ENOENT on toolcache hit)
PR Merged+5
Add agentic PR reviewer (gh-aw): requirement-fidelity + CARE SQL review
Commit Created+2
Merge pull request #148 from ohcnetwork/amjithtitus09-analytics-review-bot Add agentic PR reviewer (gh-aw): requirement-fidelity + CARE SQL review
Commit Created
Merge pull request #148 from ohcnetwork/amjithtitus09-analytics-review-bot
PR Reviewed+2
Add documentation for Stock in Air query at SSMM
PR Opened+1
Add agentic PR reviewer (gh-aw): requirement-fidelity + CARE SQL review
Commit Created+2
Add agentic PR reviewer (gh-aw): requirement-fidelity + CARE SQL review Agentic workflow that reviews every query PR through four lenses: JIRA requirement fidelity (branch name = ticket ID), CARE SQL correctness (defers to the ohcnetwork/skills care-sql-code-review skill), TEMPLATE.md conformance, and repo hygiene. - .github/workflows/analytics-review.md: gh-aw source. pull_request_target with base-only checkout (never PR head), JIRA secrets confined to the fetch pre-step, sqlglot lint pre-step, pinned skills checkout, safe-outputs as the only write channel. - .github/agents/analytics-review.agent.md: the four review lenses with proportionality guidance. - .github/scripts/lint_queries.py: deterministic sqlglot parse + template-structure lint of changed query docs (never fails the job). - .github/scripts/render_jira_ticket.py: ADF JSON -> markdown renderer. - .github/workflows/analytics-review.lock.yml + .github/aw/actions-lock.json: compiled with gh-aw v0.85.4, zero warnings. - README.md: PR Review Bot section; fix stale Accouting/ typo in the structure diagram (folder was consolidated in #144). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Commented
Commented
Commented
PR Reviewed+2
[ENG-896] feat: implement FEFO sorting for inventory lots in DispenseDrawer and StockLotSelector
PR Reviewed+2
[ENG-907] fix: correct formatting
PR Reviewed+2
[ENG-736] Fix Diagnostic report print is broken in Organization level
PR Opened+1
CCN beckn referral
Commit Created+2
Fix key error
Commit Created+2
feat: care_people_fe plug A CARE frontend plug that adds a facility-scoped People directory and the primary_facility patient extension contract. - People page under the facility nav, backed by care_people_be's CarePeopleViewSet (/api/care_people_be/?facility=) - Patient cards render instance and facility tags, linking through to the patient within the facility - Tag filter chip rebuilt over MultiFilterStyleTagSelector, emitting tags + tags_behavior to match core's tag filtering contract - primary_facility patient extension documented in the README Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Commit Created+2
Merge branch 'main' of https://github.com/ohcnetwork/care_people_be
Commit Created+2
Merge branch 'main' of https://github.com/ohcnetwork/care_people_be
Commit Created+2
Minor fixes, changes in extension
Issue Closed
AGENTS.md and CLAUDE.md have diverged — pick one source of truth
PR Reviewed+2
Merge AGENTS.md into CLAUDE.md for unified guidance
PR Reviewed+2
Improve clone command dependency syncing
PR Reviewed+2
[ENG-746] Hide "completed" from encounter status
PR Reviewed+2
[QA-214] Fix flaky device service history edit flow test
PR Reviewed+2
[QA-215] fix(ci): stop thank-you-note workflow failing on merged PRs
Issue Closed
Facility card: "Show on Map" link has an oversized clickable area
PR Reviewed+2
Fix "Show on Map" link oversized clickable area (fixes #16536)
PR Reviewed+2
🧹 Remove stale diagnosis__* i18n keys
PR Reviewed+2
[ENG-485] feat: refactor ReportViewer and associated routes to use associatingId and reportType for improved report handling
PR Reviewed+2
[ENG-877] ✍️ typo correction in diet preference option: "Dairy free"
PR Reviewed+2
[ENG-220] Enhancement in Patientcard in queue board
PR Reviewed+2
Adding secondary reviewer for care fe
PR Reviewed+2
[ENG-784] Encounter Action button is clipping out
PR Reviewed+2
[ENG-882] Gate empty-state Create Encounter button by can_create_encounter permission
PR Reviewed+2
[ENG-581] Optimize complete service request logic by remove duplication of mutation
PR Reviewed+2
🧹 Removes non-core Encounter tab translations from en.json
PR Reviewed+2
[ENG-581] Optimize complete service request logic by remove duplication of mutation
PR Reviewed+2
[ENG-735] Add pagination in Dispense History selector
Issue Closed
Incorrect local backend credentials in README
Issue Closed
Add security response headers to the nginx deployment (parity with netlify.toml)
PR Reviewed+2
Add security response headers to the nginx deployment
Commented
PR Reviewed+2
[ENG-551] Replace all other usages of GovtOrgSelector with the new picker
PR Reviewed+2
fix: Pass hidePrefixSuffix=true to formatName for all Avatar name props
PR Reviewed+2
[ENG-797] Disable titrated dosage input for read-only medication requests
PR Reviewed+2
[ENG-774] Fix Patient Registration Update redirection on submit