List assigned mentors for the team leader

[dhinesh-kumar-m]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @dhinesh-kumar-m, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the developer experience by introducing standardized templates for Git operations and begins the development of a new 'Team Lead Assigned Mentors' section. It also delivers a detailed and interactive interface for mentors to manage and track daily test performance and student follow-ups, improving oversight and engagement.

Highlights

• Developer Workflow Standardization: Introduced new cursor command templates for creating consistent Git commits and well-structured Pull Requests, aiming to streamline developer workflows and improve code quality.
• Team Lead Mentors Page: Added the initial page structure for a 'Team Lead Assigned Mentors' view, laying the groundwork for future mentor management features.
• Mentor Daily Tests UI: Implemented a comprehensive UI for mentors to view daily test details, including attempted and not-attempted student lists, follow-up tracking, and filtering capabilities.
• Theme Management: Added client-side JavaScript to base.html to manage light/dark theme preferences based on local storage and system settings.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://testpress.github.io/design/pr-preview/pr-703/
Built to branch gh-pages at 2026-03-13 09:41 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[gemini-code-assist]

Code Review

This PR introduces helpful cursor command templates and lays the groundwork for new mentor and team lead pages. The changes are extensive, adding several new HTML templates and JSON data files for prototyping. My review focuses on improving code correctness, consistency, and maintainability. Key findings include inconsistent date formats in JSON data, several instances of duplicated HTML id attributes within loops which will break functionality, and some copy-paste errors in templates. Addressing these issues will improve the robustness and clarity of the new features.

[gemini-code-assist]

The id attributes for elements inside the student details popover (e.g., hs-pro-shmaccl) are duplicated for each student in the loop. This will cause the clipboard copy functionality to fail for all but the first student in the list.

To resolve this, ensure each id is unique by appending the student's ID, like so:

<span id="hs-pro-shmaccl-{{ not_attempted_student.id }}">{{ not_attempted_student.enrollment_id }}</span>
...
<button ... data-clipboard-target="#hs-pro-shmaccl-{{ not_attempted_student.id }}">

This needs to be applied to all IDs and data-clipboard-target attributes within the loop.

[gemini-code-assist]

The id attributes for elements inside this student details popover (e.g., hs-pro-shmaccl, hs-pro-shmaccl-2, hs-pro-shmaccl-3) are duplicated for each student in the loop. This will break functionality that relies on unique IDs, such as the clipboard copy feature, which will only work for the first student.

To fix this, you should make these IDs unique, for example by appending the student's ID:

<!-- Example for Enrollment ID -->
<span id="hs-pro-shmaccl-{{ attempted_student.id }}">{{ attempted_student.enrollment_id }}</span>
...
<button ... data-clipboard-target="#hs-pro-shmaccl-{{ attempted_student.id }}">

Please apply this pattern to all duplicated IDs and their corresponding data-clipboard-target attributes within this loop.

[gemini-code-assist]

The for attribute of this label (hs-pro-eadmnm) does not match the id of the textarea it is for (hs-pro-epii). This breaks accessibility and prevents users from clicking the label to focus on the textarea.

Suggested change

	<label for="hs-pro-eadmnm" class="block mb-2 text-sm font-medium text-stone-800 dark:text-white">
	<label for="hs-pro-epii" class="block mb-2 text-sm font-medium text-stone-800 dark:text-white">

[gemini-code-assist]

The link to "View Details" is hardcoded and will always point to the same detail page. It should be made dynamic by including the specific test.id in the URL to ensure it navigates to the correct test's detail page.

        <a href="{{'/simba/mentor/daily_tests/detail/'|url}}{{test.id}}"

[gemini-code-assist]

The ID hs-pro-eptprs is duplicated. It's used here for the "Completed At" column and also for the "Incorrect" column on line 94. HTML IDs must be unique within a document to ensure scripts and styles function correctly.

                <button id="hs-pro-eptca" type="button"

[gemini-code-assist]

The completed_at timestamp is in a human-readable format ("Jan 2, 2026 6:42 PM"). For better consistency and easier machine parsing, consider using the ISO 8601 format, similar to cutoff_at on line 6. This will prevent potential issues with date/time parsing and manipulation in JavaScript.

[gemini-code-assist]

The scheduled_at field uses a custom string format ("Jan 02, 2026 · 04:00 PM"). Using a standard format like ISO 8601 would make the data more consistent and easier to parse programmatically across the application.

[gemini-code-assist]

The last_followup_at timestamp uses a human-readable format ("Jan 3, 2026 9:30 AM"). To maintain consistency across the application and simplify parsing, it's recommended to use the ISO 8601 format for all date-time strings, which is more machine-readable.

[gemini-code-assist]

There appears to be a copy-paste error in the condition for setting the active state of the "Overview" menu item. The URL being checked is for the "Franchise Head" dashboard instead of the "Mentor" dashboard.

        <a class="flex gap-x-3 lg:gap-x-1.5 py-2 px-3 w-full lg:w-auto items-center text-sm text-start text-stone-800 rounded-lg hover:bg-stone-100 disabled:opacity-50 disabled:pointer-events-none focus:outline-hidden focus:bg-stone-100 dark:text-neutral-200 dark:hover:bg-neutral-700 dark:focus:bg-neutral-700 {% if page.url == '/simba/mentor/dashboard/' %}bg-stone-100 focus:bg-stone-200 dark:bg-neutral-700 dark:focus:bg-neutral-600{% endif %} "

[gemini-code-assist]

The frontmatter sets role: "Mentor", but the file path is team_lead/.... This is inconsistent. If this page is intended for Team Leads, the role should be updated to "Team Lead" to avoid confusion and ensure any role-based logic functions correctly.

role: "Team Lead"