Generate pull request descriptions

Vague pull request descriptions like “fix bug” slow reviews and hide the purpose of a change. Use DinoAI’s pre-built .dinoprompt to generate a detailed description from the diff between your branch and main.

Prerequisites

A DinoAI Copilot session open in the Code IDE.
An active git branch with committed changes that differ from your main branch.

Estimated time: 5 minutes.

Steps

Open DinoAI

Open DinoAI from the icon in the right panel.

Open the prompt shortcut

Open the prompt picker with the prompt button ([) in the DinoAI panel. If you don’t already have a .dinoprompts file, Paradime offers to create one for you.

Select the pre-built prompt

Choose the pre-built prompt Generate a pull request description.

DinoAI prompt picker with the Generate a pull request description option selected

This prompt is pre-configured in your .dinoprompts file and can be updated to match your team’s standards. It automatically uses {{ git_diff_dinoai_test }} to include all changes between your current branch and main.

Review the generated description

Review the generated description with all sections included.

Copy into your git platform and open the PR

Copy the markdown output, paste it into your git platform (for example, GitHub), and create your pull request using the generated description.

DinoAI automatically passes the diff between your current branch and main as context using {{ git_diff_dinoai_test }}, analyzes all modified, added, and removed code to understand the scope, and generates a description with summaries, detailed change lists, and context for reviewers.

Example output

DinoAI generates professional pull request descriptions like this to copy and paste into your git platform:

## Summary
Fixed invalid column identifier causing runtime errors in race analysis models and updated column naming for consistency.

## Changes Made
- Corrected `race_id` column reference in intermediate race results model
- Renamed `driver_name` to `driver_full_name` for clarity
- Updated `championship_position` to `championship_ranking_position`
- Modified `circuit_reference` field naming for consistency
- Resolved merge conflicts with concurrent changes

## Files Modified
- `models/intermediate/int_race_results.sql`
- `models/staging/stg_drivers.sql`
- `models/marts/mart_championship_standings.sql`

## Testing
- All models compile successfully
- Runtime errors resolved
- Column naming follows established conventions

## Impact
- Fixes production pipeline failures
- Improves data model readability
- Maintains consistency with existing naming patterns

You’ll know it worked when DinoAI returns a structured description covering the actual files and changes on your branch. If the output is empty or generic, confirm your branch has committed changes that differ from main.

Next steps

Fix errors with Jira

Track and resolve errors as Jira issues from DinoAI.

Set up .dinorules from your project

Codify your team’s conventions for consistent output.

All DinoAI use cases

Browse every DinoAI Copilot workflow.

DinoAI Copilot reference

Context, tools, and features that power these workflows.

Foundations

Automate with AI agents

Set up & configure

Orchestrate data pipelines

Migrate to Paradime

Develop in Paradime

Learn dbt™

Generate pull request descriptions

Steps

Example output

Next steps

Fix errors with Jira

Set up .dinorules from your project

All DinoAI use cases

DinoAI Copilot reference

​Steps

​Example output

​Next steps

Fix errors with Jira

Set up .dinorules from your project

All DinoAI use cases

DinoAI Copilot reference

Steps

Example output

Next steps