# Why I think we should write our own PR descriptions

DevFeed: [Why I think we should write our own PR descriptions](<https://devfeed.tech/articles/why-i-think-we-should-write-our-own-pr-descriptions-3990.md>)

Original publisher: [Read original article](<https://laravel.com/blog/why-i-think-we-should-write-our-own-pr-descriptions>)

Author: Ryan Chandler

Published: 2026-09-10T12:15:00Z

Content type: opinion

Language: en

Sources: [Laravel Blog](<https://devfeed.tech/sources/laravel-blog.md>)

Topics: [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [claude](<https://devfeed.tech/tags/claude.md>), [codex](<https://devfeed.tech/tags/codex.md>), [developers](<https://devfeed.tech/tags/developers.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [review](<https://devfeed.tech/tags/review.md>), [writing](<https://devfeed.tech/tags/writing.md>)

## AI overview

The article argues that developers should write their own pull request descriptions even when AI agents implement most of a change. Writing serves as a checkpoint for understanding the change and gives reviewers human context beyond an agent-generated diff summary.

## Source excerpt

Agents can write your PR descriptions, but they shouldn't. Here's why writing them yourself makes you a better engineer and a better teammate.