GitLab Well Architected
Cookbook navigation
Prompts / Code Suggestion Adoption During Rollout

Code Suggestion Adoption During Rollout

AnalyticsCode-SuggestionsReportingAdoptionAnalyzeAdvanced

Measure code suggestion adoption across baseline and rollout windows to track progress, compare acceptance rates, and identify trends by language and IDE.

For Duo Data Analyst

prompt

You are analysing code suggestion adoption for [TEAM/ORG] to measure the impact of a GitLab Duo rollout.

Scope:
- Top-level group: [GROUP]
- Query code suggestion analytics across all projects in this group.

Time windows:
  - Baseline: [BASELINE_START] to [BASELINE_END]
  - Rollout: [ROLLOUT_START] to [ROLLOUT_END]

Instructions:

1. Query code suggestion metrics for the baseline and rollout windows, broken down by programming language. Include total suggestions, accepted count, and acceptance rate.

2. Query the same metrics broken down by IDE.

3. For each breakdown and window, compare:
  - Total suggestion volume
  - Acceptance rate
  - Active user count

4. Produce a comparison table with baseline vs rollout metrics and percentage change.

5. Add a short narrative covering:
  - where adoption increased, decreased, or stayed flat
  - which languages and IDEs saw the strongest uptake
  - caveats such as small sample size, partial windows, uneven participation, or missing data

6. Include the GLQL queries used so they can be reused in issues or docs.

Constraints:
  - Do not present this as a full productivity analysis.
  - Do not infer code quality or developer efficiency from suggestion volume alone.
  - Acceptance rate can vary by language complexity, IDE integration maturity, and team familiarity.

Use the prompt

Use comparable date ranges and identify the group whose analytics you want to examine. Keep missing data visible in the comparison; a change in suggestion acceptance doesn't by itself establish a return on the rollout.