Comprehensive review pr enhance

Skill pinkpixel-dev/skills-collection-1/SKILLS/comprehensive-review-pr-enhance

Part 1 of a large AI and agent skills collection featuring 900+ reusable skill folders, prompt workflows, references, scripts, and assets across engineering, cloud, security, research, writing, design, and automation.

Install

npx -y skills add pinkpixel-dev/skills-collection-1 --skill comprehensive-review-pr-enhance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.3 KB, 472 tokens by cl100k_base, as published. Nobody here has run it

Pull Request Enhancement

Workflow

Run git diff <base>...HEAD --stat to identify changed files and scope
Categorise changes: source, test, config, docs, build, styles
Generate the PR description using the template below
Add a review checklist based on which file categories changed
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