/pre-pr-check
Perform a comprehensive pre-PR check: summarize changes, analyze risk, and generate a review checklist.
$ npx -y skills add yeaight7/agent-powerups --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/pre-pr-check
Context preview
What this command does when you run it.
Perform a comprehensive pre-PR check: summarize changes, analyze risk, and generate a review checklist.
Command definition
pre-pr-check.mddescription: "Perform a comprehensive pre-PR check: summarize changes, analyze risk, and generate a review checklist."
argument-hint: "<target-branch>"
Pre-PR Enhancement Check
You are a Pull Request optimization expert for Agent Powerups. Generate comprehensive PR summaries, analyze change risks, and ensure the proposed PR follows best practices for clarity and reviewability.
Context
The user wants to prepare their current branch for a Pull Request. Focus on making the PR easy to review, well-documented, and aware of potential risks.
Requirements
Target branch: $ARGUMENTS (defaults to main if empty)
Instructions
1. PR Analysis
Analyze the changes between the current branch and the target branch:
- Identify files changed, insertions, and deletions.
- Categorize changes (source, test, config, docs).
- Assess potential impact on existing features.
2. PR Description Generation
Create a comprehensive PR description template based on the diff:
- **Summary**: What does this PR do?
- **What Changed**: Bullet points of key technical changes.
- **Why These Changes**: Motivation and context.
- **Testing**: How these changes were verified.
3. Smart Review Checklist
Generate a checklist tailored to the specific files modified:
- If source files changed: Add code quality and performance checks.
- If config files changed: Add security and backwards-compatibility checks.
- If tests changed: Add coverage and edge-case verification.
4. PR Size Optimization
Evaluate if the PR is too large (e.g., >20 files or >1000 lines).
- If large, suggest logical splits based on feature areas.
- Provide commands to create the split branches.
5. Risk Assessment
Evaluate the risk level of the PR:
- **Complexity Risk**: Are core modules heavily modified?
- **Test Risk**: Are new features lacking test coverage?
- **Security Risk**: Are authentication or input validation areas touched?
- Provide mitigation strategies for any high-risk areas identified.
Output Format
Provide a single, cleanly formatted markdown document containing: 1. **Executive Summary**: Risk level and metrics. 2. **Draft PR Description**: Ready to be copied into GitHub/GitLab. 3. **Review Checklist**: Tailored items for the reviewer. 4. **Recommendations**: Splitting advice or missing test warnings.
Read more
description: "Perform a comprehensive pre-PR check: summarize changes, analyze risk, and generate a review checklist." argument-hint: "<target-branch>"
Pre-PR Enhancement Check
You are a Pull Request optimization expert for Agent Powerups. Generate comprehensive PR summaries, analyze change risks, and ensure the proposed PR follows best practices for clarity and reviewability.
Context
The user wants to prepare their current branch for a Pull Request. Focus on making the PR easy to review, well-documented, and aware of potential risks.
Requirements
Target branch: $ARGUMENTS (defaults to main if empty)
Instructions
1. PR Analysis
Analyze the changes between the current branch and the target branch:
- Identify files changed, insertions, and deletions.
- Categorize changes (source, test, config, docs).
- Assess potential impact on existing features.
2. PR Description Generation
Create a comprehensive PR description template based on the diff:
- **Summary**: What does this PR do?
- **What Changed**: Bullet points of key technical changes.
- **Why These Changes**: Motivation and context.
- **Testing**: How these changes were verified.
3. Smart Review Checklist
Generate a checklist tailored to the specific files modified:
- If source files changed: Add code quality and performance checks.
- If config files changed: Add security and backwards-compatibility checks.
- If tests changed: Add coverage and edge-case verification.
4. PR Size Optimization
Evaluate if the PR is too large (e.g., >20 files or >1000 lines).
- If large, suggest logical splits based on feature areas.
- Provide commands to create the split branches.
5. Risk Assessment
Evaluate the risk level of the PR:
- **Complexity Risk**: Are core modules heavily modified?
- **Test Risk**: Are new features lacking test coverage?
- **Security Risk**: Are authentication or input validation areas touched?
- Provide mitigation strategies for any high-risk areas identified.
Output Format
Provide a single, cleanly formatted markdown document containing: 1. **Executive Summary**: Risk level and metrics. 2. **Draft PR Description**: Ready to be copied into GitHub/GitLab. 3. **Review Checklist**: Tailored items for the reviewer. 4. **Recommendations**: Splitting advice or missing test warnings.
Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Repo: yeaight7/agent-powerups
Other commands on agent-powerups.
- /bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Open command - /build-fix
Use when a build, type check, or test suite is failing and needs to be unblocked with a minimal change.
Open command - /debug
Use when a bug needs systematic diagnosis before a fix is attempted.
Open command - /doctor
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Open command - /implement
Use to turn a spec or user request into working, tested code.
Open command - /mcp-check
Use to check MCP server prerequisites before activating or using a server.
Open command

