Pull Requests Agent Skill

>- Create and review pull requests following project standards including title format, description template, and review checklist. Use when creating PRs, writing PR descriptions, or reviewing pull requests.

527 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

8685

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/redis/RedisInsight --skill pull-requests

The instruction itself

8 sections, as written by the author

Pull Request Guidelines

Creating a PR

PR Title

Include issue number at the start:

RI-123 Add user profile editing
#456 Fix memory leak in connection pool

PR Description Template

# What

Describe what was changed.

# Testing

Describe how to test the changes.

---

Refs #RI-123

PR Description Guidelines:

Keep it concise - Avoid verbose descriptions
Focus on high-level changes - Don't list every code change in the #What section
Brief and to the point - The diff shows the details; describe the "why" and "what" at a high level
Technical decisions - Only mention significant architectural or design decisions if relevant
Link, don't auto-close - Use Refs #RI-123 / Addresses #RI-123, not Closes/Fixes/Resolves - those keywords auto-close the issue when the PR merges, and tickets should be closed manually, not by the merge

Review Process

As PR Author

Respond to all comments - Address every piece of feedback
Don't take feedback personally - Reviews improve code quality
Update code based on feedback - Make requested changes
Mark conversations as resolved - After addressing feedback
Keep PR up to date - Rebase on main regularly

As PR Reviewer

Be constructive and respectful - Focus on improvement
Focus on logic, not style - Linter handles formatting
Check for:
Logic errors and edge cases
Performance issues
Security concerns
Test coverage
Missing documentation
Architectural concerns

Review Checklist

[ ] Code follows project patterns
[ ] Tests are comprehensive
[ ] No console.log or debug code
[ ] TypeScript types are proper
[ ] Error handling is adequate
[ ] Documentation is updated
[ ] No security vulnerabilities
[ ] Performance is acceptable

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take redis/pull-requests from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.