Automated summary
Generates comprehensive pull request descriptions, automates review processes, and ensures PRs follow best practices for clarity, size, and reviewability.
Strengths
- Provides clear analysis of changes and intent
- Includes test coverage and risk assessment
- Facilitates faster code reviews with structured output
- Offers templates and checklists for consistency
Limitations
- Relies on having access to the diff or change list
- Does not replace a full code review
- May require manual adjustment for specific project conventions
When you need to create or improve a pull request description with thorough documentation and review-ready structure.
When there is no PR or change list to summarize, or when a complete code review is needed instead of PR polishing.
Security analysis
SafeThe skill provides guidance on creating pull request descriptions and facilitating reviews, with no executable commands or tools declared. It does not instruct any file system modifications, network calls, or sensitive data handling.
No concerns found
How this analysis is madeExamples
Write a PR description for the following branch diff that summarizes changes, tests, and risks.Improve the existing PR description with a change log, test results, and reviewer checklist.Analyze the diff and generate a PR summary with scope, breaking changes, and rollout notes.version: 4.1.0-fractal name: comprehensive-review-pr-enhance description: "You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability."
Pull Request Enhancement
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.
Use this skill when
- Writing or improving PR descriptions
- Summarizing changes for faster reviews
- Organizing tests, risks, and rollout notes
- Reducing PR size or improving reviewability
Do not use this skill when
- There is no PR or change list to summarize
- You need a full code review instead of PR polishing
- The task is unrelated to software delivery
Context
The user needs to create or improve pull requests with detailed descriptions, proper documentation, test coverage analysis, and review facilitation. Focus on making PRs that are easy to review, well-documented, and include all necessary context.
Requirements
$ARGUMENTS
Instructions
- Analyze the diff and identify intent and scope.
- Summarize changes, tests, and risks clearly.
- Highlight breaking changes and rollout notes.
- Add checklists and reviewer guidance.
- If detailed templates are required, open
resources/implementation-playbook.md.
Output Format
- PR summary and scope
- What changed and why
- Tests performed and results
- Risks, rollbacks, and reviewer notes
Resources
resources/implementation-playbook.mdfor detailed templates and examples.
🧠 Knowledge Modules (Fractal Skills)
1. implementation-playbook
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/pull-request-enhancement-mm78noab/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/pull-request-enhancement-mm78noab' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pull-request-enhancement-mm78noab/download' --output '.skill-downloads/pull-request-enhancement-mm78noab/SKILL.md.part' && mv '.skill-downloads/pull-request-enhancement-mm78noab/SKILL.md.part' '.skill-downloads/pull-request-enhancement-mm78noab/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Original excerpt: Requirements
$ARGUMENTS
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/pull-request-enhancement-mm78noab/SKILL.md' && test -s '.skill-downloads/pull-request-enhancement-mm78noab/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/comprehensive-review-pr-enhance' && cp -R '.skill-downloads/pull-request-enhancement-mm78noab' '.claude/skills/comprehensive-review-pr-enhance'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/pull-request-enhancement-mm78noab'openskills read 'pull-request-enhancement-mm78noab'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/pull-request-enhancement-mm78noab/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.