Skip to content
Skillpedia
Documentation48k · #2612

comprehensive-review-pr-enhance

Lets your agent create clear descriptions for code reviews (PRs). It adds checklists and summaries to help reviewers understand changes.

What it does

This tool helps create clear and organized descriptions for the changes you've made in a programming project (called 'pull requests' or PRs). It also suggests checks for code reviewers.

When to use it

  • ✓When you need to explain your changes for others to review.
  • ✓If you have many changes and need a detailed description.
  • ✓To ensure the code review is thorough and covers risks.

Example of what to ask your AI

“Write a description for this pull request based on my code changes.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/comprehensive-review-pr-enhance/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/comprehensive-review-pr-enhance/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool analyzes your code changes, organizes them by type (like new code, tests, or configurations), and builds a structured summary. It also adds a checklist for reviewers based on the types of files modified.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill comprehensive-review-pr-enhance

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/comprehensive-review-pr-enhance/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Pull Request Enhancement

When to Use

  • You need to turn a git diff into a reviewer-friendly pull request description.
  • You want a PR summary with change categories, risks, testing notes, and a checklist.
  • The diff is large enough that reviewers need explicit structure instead of a short ad hoc summary.

Workflow

  1. Run git diff <base>...HEAD --stat to identify changed files and scope
  2. Categorise changes: source, test, config, docs, build, styles
  3. Generate the PR description using the template below
  4. Add a review checklist based on which file categories changed
  5. Flag breaking changes, security-sensitive files, or large diffs (>500 lines)

PR Description Template

## Summary
<!-- one-paragraph executive summary: what changed and why -->

## Changes
| Category | Files | Key change |
|----------|-------|------------|
| source   | `src/auth.ts` | added OAuth2 PKCE flow |
| test     | `tests/auth.test.ts` | covers token refresh edge case |
| config   | `.env.example` | new `OAUTH_CLIENT_ID` var |

## Why
<!-- link to issue/ticket + one sentence on motivation -->

## Testing
- [ ] unit tests pass (`npm test`)
- [ ] manual smoke test on staging
- [ ] no coverage regression

## Risks & Rollback
- **Breaking?** yes / no
- **Rollback**: revert this commit; no migration needed
- **Risk level**: low / medium / high — because ___

Review Checklist Rules

Add checklist sections only when the matching file category appears in the diff:

File category Checklist items
source no debug statements, functions <50 lines, descriptive names, error handling
test meaningful assertions, edge cases, no flaky tests, AAA pattern
config no hardcoded secrets, env vars documented, backwards compatible
docs accurate, examples included, changelog updated
security-sensitive (auth, crypto, token, password in path) input validation, no secrets in logs, authz correct

Splitting Large PRs

When diff exceeds 20 files or 1000 lines, suggest splitting by feature area:

git checkout -b feature/part-1
git cherry-pick <commits-for-part-1>

Resources

  • resources/implementation-playbook.md — Python helpers for automated PR analysis, coverage reports, and risk scoring

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
FAQ

What is a 'git diff'?

It's a command that shows the differences between two versions of your code.

What is a 'pull request' (PR)?

It's a request for others to review and accept the changes you've made to a project's code.

Why organize the PR description?

An organized description makes changes easier to understand, speeds up the review process, and helps identify potential issues or risks.

Details

Original description by the author

Generate structured PR descriptions from diffs, add review checklists, risk assessments, and test coverage summaries. Use when the user says "write a PR description", "improve this PR", "summarize my changes", "PR review", "pull request", or asks to document a diff for reviewers.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#2612
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills