> ## Documentation Index > Fetch the complete documentation index at: https://docs.heygarth.ai/llms.txt > Use this file to discover all available pages before exploring further. # Engineering insights ## Engineering Insights — Individual Developer The **Individual Developer** sub-tab is the default view and gives a ranked, organization-wide view of every developer's productivity. ### Filters | Filter | Description | | ---------- | ------------------------------------------------------------------------------ | | Department | Restrict the leaderboard to a specific department, or view **All Departments** | | Team | Restrict the leaderboard to a specific team, or view **All Teams** | | Developer | Jump directly to a specific developer, or view **All Developers** | | Time range | 7 / 15 / 90 days | ### Developer Leaderboard A sortable table ranking all developers by **Overall Score** (descending by default). Columns: | Column | Description | | ----------------- | ------------------------------------------------------------------------------------------------------------ | | # | Rank position | | Name | Developer's name — clickable, opens the [Developer Productivity Detail](#developer-productivity-detail) page | | Team | Team the developer is currently mapped to (or **Unassigned**) | | Commits | Total commits in the selected time range | | PRs Merged | Total pull requests merged in the selected time range | | AI Adoption Score | A 0–100 score reflecting how much of the developer's work involved AI-assisted coding tools | | Overall Score | A blended productivity score (0–100) combining commit activity, PR activity, and AI adoption | The table supports column-level sorting, a developer search box, and a **View Full List** option to expand beyond the default rows shown. ### AI Adoption vs Overall Score (chart) A scatter/bubble chart plotting each developer's **AI Adoption Score** (x-axis) against their **Overall Score** (y-axis), for the currently filtered scope. Each bubble represents one developer. This view is intended to visually surface whether higher AI tool adoption correlates with higher overall productivity across the organization. ### Developer Scorecard (chart) A simple three-bar comparison chart showing: * **Top Performer** — the highest Overall Score in the current filter scope * **Average** — the mean Overall Score across all developers in scope * **Low** — the lowest Overall Score in the current filter scope This gives an at-a-glance spread of performance across the organization (or the filtered department/team) without needing to scan the full leaderboard. *** ## Developer Productivity Detail Clicking any developer's name from the leaderboard opens their **Developer Productivity Detail** page — a dedicated, single-developer view of the same underlying metrics, broken down further. ### Header summary * Developer name and team * **Strongest** area (e.g. *Commit Performance*) and **Focus area** (e.g. *AI-Assisted Development*) — auto-identified highlights * **Overall Score**, with a trend delta (e.g. *+10.8*) versus the prior period * **Team Rank** (e.g. 1/2) and **Department Rank** (e.g. 1/5) for Overall Score * Time range toggle (7d / 15d / 90d), scoped to this page only ### Commit Performance | Metric | Description | | ---------------------- | ----------------------------------------------------- | | Commits | Total commit count in the selected range | | Team Rank | Developer's commit-count rank within their team | | Department Rank | Developer's commit-count rank within their department | | Days Since Last Commit | Recency indicator | Charts: * **Commit Performance Trend** — daily commit count over the selected range * **PR Performance Trend** — daily PRs created vs. PRs merged * **Avg Merge Time Trend** — average time (in minutes) between PR creation and merge, tracked daily ### Code Contribution | Metric | Description | | --------------------------- | ------------------------------------------- | | Commit Lines Added | Total lines added across commits in range | | Commit Lines Removed | Total lines removed across commits in range | | Team Rank / Department Rank | Rank by contribution volume | > Volume is a contextual signal, not a quality measure. Chart: * **Code Contribution Trend** — daily lines added vs. lines removed ### AI-Assisted Development | Metric | Description | | --------------------------- | ------------------------------------------------ | | Score | 0–100 score reflecting AI tool usage intensity | | Acceptance Rate | % of AI-suggested code accepted by the developer | | Team Rank / Department Rank | Rank by AI-assisted development score | Chart: * **AI-Assisted Development Trend** — daily acceptance rate over the selected range ### Collaboration | Metric | Description | | ---------------------- | -------------------------------------------- | | Reviews Given | Number of PR reviews the developer performed | | PR Approvals | Number of PRs approved | | Review Comments | Number of comments left during reviews | | Merges Performed | Number of merges the developer carried out | | Days Since Last Review | Recency indicator | Chart: * **Collaboration Trend** — daily review activity count ### Peer Comparison A table comparing the developer's own metrics against their team average, for the same time range: | Metric | My Score | Team Avg Score | Team Rank | | --------------------- | -------- | -------------- | --------- | | Commits | | | | | PR Opened | | | | | PR Merged | | | | | Avg Merge Time (mins) | | | | | Lines Added | | | | | Lines Removed | | | | | AI Code Acceptance | | | | | AI Adoption Score | | | | This lets the developer (or their manager) see at a glance which specific metrics are above or below the team average, rather than relying on the single blended Overall Score alone. ## Engineering Insights — Team The **Team** sub-tab rolls the same underlying metrics up to team level, letting you compare teams against each other instead of individuals. ### Filters | Filter | Description | | ---------- | ------------------------------------------------------------------------------------------- | | Department | Restrict the leaderboard to teams within a specific department, or view **All Departments** | | Team | Jump directly to a specific team, or view **All Teams** | | Time range | 7 / 15 / 90 days | There is no individual-developer filter here, since the view is already scoped one level above it. ### Team Leaderboard A sortable table ranking all teams by **Overall Score** (descending by default). Columns: | Column | Description | | ----------------- | ---------------------------------------------------------------------------------------------------------------------- | | # | Rank position | | Team | Team name — clickable (e.g. **G360 Team**, **Healix team**), or **Unassigned** for developers not yet mapped to a team | | Commits | Total commits by the team's developers in the selected time range | | PRs Merged | Total pull requests merged by the team in the selected time range | | AI Adoption Score | Team-average AI Adoption Score | | Overall Score | Blended productivity score (0–100) for the team, combining commit activity, PR activity, and AI adoption | Same search box and **View Full List** affordance as the Individual Developer leaderboard. ### AI Adoption vs Overall Score (chart) Same scatter/bubble format as the Individual Developer view, except each bubble now represents one **team** rather than one developer — plotting team-average AI Adoption Score (x-axis) against team Overall Score (y-axis). ### Team Scorecard (chart) A three-bar comparison chart showing: * **Top Team** — the highest Overall Score among teams in the current filter scope * **Average** — the mean Overall Score across teams in scope * **Low** — the lowest Overall Score among teams in scope *** ## Engineering Insights — Department The **Department** sub-tab rolls metrics up one level further, to department level — the highest level of aggregation in Engineering Insights. ### Filters | Filter | Description | | ---------- | ------------------------------------------------------------------- | | Department | Jump directly to a specific department, or view **All Departments** | | Time range | 7 / 15 / 90 days | This is the top of the hierarchy, so there's no Team or Developer filter at this level. ### Department Leaderboard A sortable table ranking all departments by **Overall Score** (descending by default). Columns: | Column | Description | | ----------------- | ------------------------------------------------------------------------------------------------------------------- | | # | Rank position | | Department | Department name — clickable (e.g. **Engineering**), or **Unassigned** for developers not yet mapped to a department | | Commits | Total commits across the department's developers in the selected time range | | PRs Merged | Total pull requests merged across the department in the selected time range | | AI Adoption Score | Department-average AI Adoption Score | | Overall Score | Blended productivity score (0–100) for the department | ### AI Adoption vs Overall Score (chart) Same scatter/bubble format again, with each bubble now representing one **department** — department-average AI Adoption Score (x-axis) against department Overall Score (y-axis). ### Department Scorecard (chart) A three-bar comparison chart showing: * **Top Department** — the highest Overall Score among departments in scope * **Average** — the mean Overall Score across departments in scope * **Low** — the lowest Overall Score among departments in scope *** ## Hierarchy summary The three sub-tabs represent the same underlying metrics (Commits, PRs Merged, AI Adoption Score, Overall Score) aggregated at three levels: \`\`\` Department → Team → Individual Developer \`\`\` Only the **Individual Developer** leaderboard supports drilling into a single row for a full Developer Productivity Detail breakdown; Team and Department rows are aggregation points for comparison and do not currently have an equivalent drill-down page.