My 7 favorite code review AI prompts:

by Feb 22, 2024

My 7 favorite code review AI prompts:

I often work in two separate modes when coding: Writing and Reviewing.

In reviewing (editing) I focus on cleaning up, shortening and improving the code. I use the following AI prompts:

1️⃣ Suggest Refactoring. Proposes too much breaking up a method into multiple tiny methods for my liking, but sometimes it gives a valuable insight.

2️⃣ Find Problems My code is flawless of course, but what better way to ask AI if it agrees.

3️⃣ Simplify Often code can be written simpler if you take a closer look. Propose shorter code or even one-liners.

4️⃣ Propose Better Name Naming is hard. I just ask AI to propose five names which would be a better fit.

5️⃣ Improve Performance Often code is already good enough and it proposes micro-optimizations. But once in a while it detects a performance issue, which is often easy to solve.

6️⃣ Write Documentation Often forgotten and time consuming but it helps other devs a lot. Let AI do it!

7️⃣ Write Commit Message AI now writes all my commits. It is so much better than me. Try it!

What is your favorite code review AI prompt?

#
Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more