Pr Retro

After a pull request is merged or rejected, you can learn what went right and what went wrong. This skill helps you spot patterns in your code reviews. It looks at feedback from reviewers, checks if tests were missing, and finds ways to improve your next pull request. You get a short report each time so you can keep getting better over time.

The tool works with GitHub’s gh command and git. You run a few commands to find your recent pull requests, read the comments, and see if they were accepted or rejected. Then it saves a learning note with the date, the repo name, and what happened. This is useful for any developer who wants to avoid repeating the same mistakes and build stronger habits.

By reviewing your own contributions regularly, you can catch issues like too large a pull request, missing documentation, or ignored feedback. This makes you a better teammate and helps your whole team move faster. The skill works best when you use it after every important pull request or once a week to see your overall pattern.