chore(profile): add profile for Samiksha

[samiksha16]

Added my profile for close #715

Summary by CodeRabbit

• New Features
  • Added a new team profile for Samiksha Kushwah (GitHub: samiksha-kushwah). The profile now appears at the start of the team directory and includes a reference to a related GitHub trial issue for context. No existing profiles were changed or removed.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

A new team profile object for Samiksha Kushwah (github_handle "samiksha-kushwah") was inserted at the start of the "team_profiles" array in profile-submission.json. No other entries were modified or removed.

Changes

Cohort / File(s)	Change Summary
Team profiles JSON profile-submission.json	Inserted a new team profile object for "Samiksha Kushwah" (github_handle: samiksha-kushwah, includes github_trial_issue_link) at the beginning of the team_profiles array.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single-file, additive JSON change with no logic or schema alterations.

Possibly related PRs

• chore(profile): add profile for mohak #698 — Adds a new team profile object to the beginning of profile-submission.json (same insertion pattern).
• chore(profile): add profile for Kamal Abdul #167 — Also adds a new entry to profile-submission.json's team_profiles array.
• chore(profile): add Gyanshu Pathak profile #42 — Inserts a new team profile entry at the start of the same JSON array.

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title clearly and concisely describes the main change: adding a profile for Samiksha to the team directory.
Linked Issues check	✅ Passed	The PR successfully implements the objective from issue #715 by adding a new team profile entry for Samiksha Kushwah to profile-submission.json.
Out of Scope Changes check	✅ Passed	All changes are in-scope; only a single new profile entry was added to profile-submission.json as required by issue #715.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c19f839 and 2f12852.

📒 Files selected for processing (1)

• profile-submission.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• profile-submission.json

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

profile-submission.json (1)

3-7: Align indentation with existing entries for consistency

All other objects use six-space indentation for the inner fields, while the newly added entry uses only two. Consistent formatting keeps the JSON readable and minimizes noise in future diffs.

3     {
-  "github_handle": "samiksha-kushwah",
-  "full_name": "Samiksha Kushwah",
-  "github_trial_issue_link": "https://github.com/holdex/trial/issues/714"
+      "github_handle": "samiksha-kushwah",
+      "full_name": "Samiksha Kushwah",
+      "github_trial_issue_link": "https://github.com/holdex/trial/issues/714"
7     },

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c3ec836 and 4918114.

📒 Files selected for processing (1)

• profile-submission.json (1 hunks)

[holdex]

Time Submission Status

Member	Status	Time	Action	Last Update
samiksha16	✅ Submitted	5min	Update time	Dec 17, 2025, 8:31 AM
tiffmyaaw	✅ Submitted	7min	Update time	Dec 17, 2025, 8:31 AM

[tiffmyaaw]

Please resolve conflicts, then rename your PR title and description based on our Guidelines

Edit the PR description to link your issue manually.

Follow this instruction to verify past commits.

Last, submit your time spent on the PR Time Tracker bot.

Feel free to look at the successfully closed PRs in this repo for refs.

[tiffmyaaw]

Hi @samiksha16 did you see my review? Will wait until the end of the week

[samiksha16]

Hi @samiksha16 did you see my review? Will wait until the end of the week

Hi @tiffmyaaw I followed the steps mentioned, let me know if I am still missing something. Thanks!